Re: [BUGS] BUG #14694: Long binded parameter value in the postgres log
От | Pavel Stehule |
---|---|
Тема | Re: [BUGS] BUG #14694: Long binded parameter value in the postgres log |
Дата | |
Msg-id | CAFj8pRCSfVyOPGJxO34FE+zNZNxhN7Jdsznq+0=p2vVEiPg2+A@mail.gmail.com обсуждение исходный текст |
Ответ на | [BUGS] BUG #14694: Long binded parameter value in the postgres log (nikolay.nikitin@infowatch.com) |
Список | pgsql-bugs |
Hi
2017-06-07 9:25 GMT+02:00 <nikolay.nikitin@infowatch.com >:
The following bug has been logged on the website:
Bug reference: 14694
Logged by: Nikolay Nikitin
Email address: nikolay.nikitin@infowatch.com
PostgreSQL version: 9.6.3
Operating system: Red Hat Enterprise Linux Server release 6.7
Description:
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 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.
It is not a bug - although it is great very practical idea. Please, send it to pgsql-hackers@postgresql.org mailing list.
Regards
Pavel
Regards,
Nikolay.
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
В списке pgsql-bugs по дате отправления: