Ygthkb

Why does alert(0.-5) print -5?

What does an unprocessed RAW file look like?

What's the reason that we have a different number of days each month?

The No-Straight Maze

Why are mages sometimes played bot instead of traditional ADCs?

Buying a "Used" Router

Insecure private-key encryption

XOR-free sets: Maximum density?

How do dictionaries source attestation?

What are some ways of extending a description of a scenery?

Count repetitions of an array

Do we still track damage on indestructible creatures?

How can I handle players killing my NPC outside of combat?

What is an efficient way to digitize a family photo collection?

Should a new user just default to LinearModelFit (vs Fit)

Democratic Socialism vs Social Democracy

Boss asked me to sign a resignation paper without a date on it along with my new contract

Why is it that Bernie Sanders is always called a "socialist"?

Is the fingering of thirds flexible or do I have to follow the rules?

Does it take energy to move something in a circle?

How can I deduce the power of a capacitor from its datasheet?

Is it legal to point a domain to someone else's ip (website)?

What does からか mean?

Why didn't Tom Riddle take the presence of Fawkes and the Sorting Hat as more of a threat?

Postgresql - limit size of logged message

Create INSERT INTO from SELECT in PostgreSQLPostgres Update LimitLimit of psql_historyHow do I limit the size of my Postgres log?Transaction Log file size for Index reorgQuery taking too much time for executing in postgresql-9.5pgAgent does not start with message “ERROR: Couldn't register event handle.”PostgreSQL Cluster vs PostgreSQL Master-Slave ReplicationPostgreSQL; Update different column on condition using CASE statementMethodFunction encryption in PostgreSQL

-2

I'm trying to overcome a problem with unreadable PostgreSQL log. There is a database that contains (unfortunately) files in column with datatype bytea (bad application design, lot of time to rework to mongo etc.).

I have configured PostgreSQL to keep track of low performing queries by setting:

log_min_duration_statement = 200 

Due to this my PostgreSQL log is filled with huge mess, something like:

2018-07-01 09:03:31 CEST DETAIL: parameters: $1 = '38007670', $2 =
'9772671', $3 = '%PDF-1.515%34234331732315121 0

obj15<</Metadata 2 0 R/OCProperties<</D<</OFF[8 0 R]/ON[9 0 R 10 0 R
11 0 R 12 0 R 13 0 R 14 0 R 15 0 R 16 0 R] ...

This can go on well over thousands of lines in the log file and it just makes the whole thing unusable.

• Is there any way to "cut" the string in the detail to some maximal size?


• Or to limit the size of the log file?

postgresql-9.5 log

share|improve this question

edited 16 mins ago

hot2use

8,35752055

asked Jul 2 '18 at 7:21

krszpkrszp

11

add a comment | 

-2

I'm trying to overcome a problem with unreadable PostgreSQL log. There is a database that contains (unfortunately) files in column with datatype bytea (bad application design, lot of time to rework to mongo etc.).

I have configured PostgreSQL to keep track of low performing queries by setting:

log_min_duration_statement = 200 

Due to this my PostgreSQL log is filled with huge mess, something like:

2018-07-01 09:03:31 CEST DETAIL: parameters: $1 = '38007670', $2 =
'9772671', $3 = '%PDF-1.515%34234331732315121 0

obj15<</Metadata 2 0 R/OCProperties<</D<</OFF[8 0 R]/ON[9 0 R 10 0 R
11 0 R 12 0 R 13 0 R 14 0 R 15 0 R 16 0 R] ...

This can go on well over thousands of lines in the log file and it just makes the whole thing unusable.

• Is there any way to "cut" the string in the detail to some maximal size?


• Or to limit the size of the log file?

postgresql-9.5 log

share|improve this question

edited 16 mins ago

hot2use

8,35752055

asked Jul 2 '18 at 7:21

krszpkrszp

11

add a comment | 

I'm trying to overcome a problem with unreadable PostgreSQL log. There is a database that contains (unfortunately) files in column with datatype bytea (bad application design, lot of time to rework to mongo etc.).

I have configured PostgreSQL to keep track of low performing queries by setting:

log_min_duration_statement = 200 

Due to this my PostgreSQL log is filled with huge mess, something like:

2018-07-01 09:03:31 CEST DETAIL: parameters: $1 = '38007670', $2 =
'9772671', $3 = '%PDF-1.515%34234331732315121 0

obj15<</Metadata 2 0 R/OCProperties<</D<</OFF[8 0 R]/ON[9 0 R 10 0 R
11 0 R 12 0 R 13 0 R 14 0 R 15 0 R 16 0 R] ...

This can go on well over thousands of lines in the log file and it just makes the whole thing unusable.

• Is there any way to "cut" the string in the detail to some maximal size?


• Or to limit the size of the log file?

postgresql-9.5 log

share|improve this question

edited 16 mins ago

hot2use

8,35752055

asked Jul 2 '18 at 7:21

krszpkrszp

11

log_min_duration_statement = 200 

share|improve this question

edited 16 mins ago

hot2use

8,35752055

asked Jul 2 '18 at 7:21

krszpkrszp

11

share|improve this question

edited 16 mins ago

hot2use

8,35752055

asked Jul 2 '18 at 7:21

krszpkrszp

11

edited 16 mins ago

hot2use

8,35752055

edited 16 mins ago

hot2use

8,35752055

asked Jul 2 '18 at 7:21

krszpkrszp

11

asked Jul 2 '18 at 7:21

krszpkrszp

11