Re: replication commands and log_statements
| От | Tom Lane |
|---|---|
| Тема | Re: replication commands and log_statements |
| Дата | |
| Msg-id | 16890.1403272111@sss.pgh.pa.us обсуждение |
| Ответ на | Re: replication commands and log_statements (Fujii Masao <masao.fujii@gmail.com>) |
| Ответы |
Re: replication commands and log_statements
Re: replication commands and log_statements |
| Список | 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 по дате отправления: