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

From Robert Haas
Subject Re: replication commands and log_statements
Date
Msg-id CA+TgmoadGAdOmnz5QXJbptNFE2zXwX7phFejv3Nbs9tb1WVozw@mail.gmail.com
Whole thread Raw
In response to Re: replication commands and log_statements  (Abhijit Menon-Sen <ams@2ndQuadrant.com>)
Responses Re: replication commands and log_statements
List pgsql-hackers
On Thu, Aug 7, 2014 at 12:07 PM, Abhijit Menon-Sen <ams@2ndquadrant.com> wrote:
> At 2014-08-07 23:22:43 +0900, masao.fujii@gmail.com wrote:
>> That is, we log replication commands only when log_statement is set to
>> all. Neither new parameter is introduced nor log_statement is
>> redefined as a list.
>
> That sounds good to me.

It sounds fairly unprincipled to me.  I liked the idea of making
log_statement a list, but if we aren't gonna do that, I think this
should be a separate parameter.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: psql: show only failed queries
Next
From: Robert Haas
Date:
Subject: Re: A worst case for qsort