Re: [HACKERS] Long binded parameter value in the postgres log

[Masahiko Sawada]

On Thu, Jun 8, 2017 at 5:00 PM, Nikitin Nikolay
 wrote:
> 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.
>

In this case, I think you can use log_error_verbosity = terse which
excludes the logging of DETAIL, HINT, QUERY, and CONTEXT error
information. On the other hand, since actually the log of particular
large SQL or its parameter sometimes presses the free capacity,
possibly it's a good idea to have such threshold.

Regards,

--
Masahiko Sawada
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

[HACKERS] Long binded parameter value in the postgres log

[Nikitin Nikolay]

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.niki...@infowatch.com
PostgreSQL version: 9.4.11