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

From Bruce Momjian
Subject Re: replication commands and log_statements
Date
Msg-id 20140808150058.GB22956@momjian.us
Whole thread Raw
In response to Re: replication commands and log_statements  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: replication commands and log_statements
List pgsql-hackers
On Fri, Aug  8, 2014 at 08:51:13AM -0400, Robert Haas wrote:
> 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.

I am unclear there is enough demand for a separate replication logging
parameter --- using log_statement=all made sense to me.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + Everyone has their own god. +



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: PENDING_LIST_CLEANUP_SIZE - maximum size of GIN pending list Re: HEAD seems to generate larger WAL regarding GIN index
Next
From: Tom Lane
Date:
Subject: Re: jsonb format is pessimal for toast compression