Re: logging of Logical Decoding

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
Cc: Andrey Lizenko <lizenko79(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: logging of Logical Decoding
Date: 2014-12-24 16:50:26
Message-ID: 8307.1419439826@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> writes:
> On 12/24/2014 07:53 AM, Andrey Lizenko wrote:
>> 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);

> What you are looking for is to eliminate logging the statement entirely?
> I would have though having log_statement = none would prevent that.

No, this isn't logging any old statement that comes along, it's logging
the statement that provoked the LOG message. That's normal behavior.

It is worth asking why these messages aren't DEBUG rather than LOG,
but I don't see anything unexpected about the form of the output.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2014-12-24 17:36:36 Re: logging of Logical Decoding
Previous Message Adrian Klaver 2014-12-24 16:27:22 Re: logging of Logical Decoding