Fujii Masao <masao.fu...@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 -- Sent via pgsql-hackers mailing list (firstname.lastname@example.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers