Re: replication commands and log_statements - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: replication commands and log_statements
Date
Msg-id CAA4eK1LYn8B7crzt_XXQLK7QM8S0vvaFtfLy-KiDgyFfeq4-ug@mail.gmail.com
Whole thread Raw
In response to Re: replication commands and log_statements  (Fujii Masao <masao.fujii@gmail.com>)
Responses Re: replication commands and log_statements
List pgsql-hackers
On Tue, Aug 12, 2014 at 9:29 AM, Fujii Masao <masao.fujii@gmail.com> wrote:
> On Tue, Aug 12, 2014 at 2:34 AM, Robert Haas <robertmhaas@gmail.com> wrote:
> >
> > If you have a user devoted to it, I suppose that's true.  I still
> > think it shouldn't get munged together like that.
>
> Why do we need to treat only replication commands as special ones and
> add new parameter to display them?

One difference is that replication commands are internally generated
commands. Do we anywhere else log such internally generated
commands with log_statement = all?


With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: postgresql.auto.conf and reload
Next
From: Michael Paquier
Date:
Subject: Re: Removing dependency to wsock32.lib when compiling code on WIndows