[HACKERS] Long binded parameter value in the postgres log - Mailing list pgsql-hackers

From Nikitin Nikolay
Subject [HACKERS] Long binded parameter value in the postgres log
Date
Msg-id 9D7DC2CE9ACC4342AF7E7A88DDD0C9330193C2BC1B@v-maildb-02.infowatch.ru
Whole thread Raw
Responses Re: [HACKERS] Long binded parameter value in the postgres log  (Masahiko Sawada <sawada.mshk@gmail.com>)
List pgsql-hackers

Hi!

 

We insert many rows with long text and bytea (about 500 MB) values. In the postgres config we set log_min_duration_statement to 120 seconds.

If this statements work more 120 seconds then they will be written into the postgres log with parameter values.

As a result, the postgres log increases by 500MB for each statement.

 

I think the postgres should have a "max bind value log size" parameter. If a bind value is bigger then this parameter, it will be truncated.

And in the log its real size and its truncated part will be written.

 

Regards,

Nikolay Nikitin.

 

Email address: nikolay.nikitin@infowatch.com

PostgreSQL version: 9.4.11

 

pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: [HACKERS] Re: Alter subscription..SET - NOTICE message is comingfor table which is already removed
Next
From: Heikki Linnakangas
Date:
Subject: [HACKERS] List of hostaddrs not supported