Re: logging of Logical Decoding

On 12/24/2014 07:53 AM, Andrey Lizenko wrote:
> I've restarted server once again to be sure.
>
> For this commands:
>
> postgres(at)ubuntu12-vm:/mnt/data4$ psql
> psql (9.4.0)
> Type "help" for help.
> postgres=# show log_error_verbosity ;
> log_error_verbosity
> ---------------------
> terse
> (1 row)
> postgres=# SELECT * FROM
> pg_logical_slot_get_changes('regression_slot', NULL, NULL);
> location | xid | data
> ----------+-----+------
> (0 rows)
>
>
> I can see the following log:
>
> 2014-12-24 10:45:01 EST LOG: database system was shut down at
> 2014-12-24 10:44:52 EST
> 2014-12-24 10:45:01 EST LOG: database system is ready to accept
> connections
> 2014-12-24 10:45:01 EST LOG: autovacuum launcher started
> 2014-12-24 10:45:23 EST LOG: starting logical decoding for slot
> "regression_slot"
> 2014-12-24 10:45:23 EST STATEMENT: SELECT * FROM
> pg_logical_slot_get_changes('regression_slot', NULL, NULL);
> 2014-12-24 10:45:23 EST LOG: logical decoding found consistent
> point at A/75000100
> 2014-12-24 10:45:23 EST STATEMENT: SELECT * FROM
> pg_logical_slot_get_changes('regression_slot', NULL, NULL);
>
>
> So it seems terse verbosity doesn't help. Bug? Or something wrong in my
> config? As I said before, it is created from scratch and almost default,
> expect log_line_prefix

Well you wanted to reduce verbosity level which is what happens when you
set to terse.

What you are looking for is to eliminate logging the statement entirely?

I would have though having log_statement = none would prevent that.

Someone else will have to comment on why that is not so?

>
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com