On 06/09/2017 02:16 PM, Ken Tanzer wrote:
> FWIW, it would be clearer at least to me if you took the two statements
> in the description:
>
> * log_statement setting is set to "all", meaning every SQL statement
> executed while in this state will also get logged.
> * If set_user.block_log_statement is set to "on", SET log_statement
> and variations will be blocked. And this one from the notes:
>
> And this one from the notes:
>
> * If set_user.block_log_statement is set to "off", the log_statement
> setting is left unchanged.
>
> And combined them together:
>
> If set-user.block_log_statement is set to "on", log_statement setting is
> set to "all", meaning every SQL statement executed while in this state
> will also get logged. SET log_statement and variations will be
> blocked. If set to "off," the log statement setting is left unchanged.
Sounds good, will make that change or something similar -- thanks for
the feedback.
Joe
--
Crunchy Data - http://crunchydata.com
PostgreSQL Support for Secure Enterprises
Consulting, Training, & Open Source Development