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

From Tom Lane
Subject Re: replication commands and log_statements
Date
Msg-id 16890.1403272111@sss.pgh.pa.us
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  (Michael Paquier <michael.paquier@gmail.com>)
Re: replication commands and log_statements  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Fujii Masao <masao.fujii@gmail.com> writes:
> OK, I've just implemented the patch (attached) which does this, i.e., redefines
> log_statement as a list. Thanks to the patch, log_statement can be set
> to "none",
> "ddl", "mod", "dml", "all", and any combinations of them. The meanings of
> "none", "ddl", "mod" and "all" are the same as they are now. New setting value
> "dml" loggs both data modification statements like INSERT and query access
> statements like SELECT and COPY TO.

I still don't like this one bit.  It's turning log_statement from a
reasonably clean design into a complete mess, which will be made even
worse after you add replication control to it.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: Audit of logout
Next
From: Haribabu Kommi
Date:
Subject: Re: [WIP] showing index maintenance on EXPLAIN