Re: replication commands and log_statements
От | Andres Freund |
---|---|
Тема | Re: replication commands and log_statements |
Дата | |
Msg-id | 20140611125606.GW8406@alap3.anarazel.de обсуждение исходный текст |
Ответ на | Re: replication commands and log_statements (Magnus Hagander <magnus@hagander.net>) |
Ответы |
Re: replication commands and log_statements
|
Список | pgsql-hackers |
On 2014-06-11 14:50:34 +0200, Magnus Hagander wrote: > On Wed, Jun 11, 2014 at 2:35 PM, Andres Freund <andres@2ndquadrant.com> > wrote: > > > On 2014-06-11 14:22:43 +0200, Magnus Hagander wrote: > > > Yes, but how would you specify for example "i want DDL and all > > replication > > > commands" (which is quite a reasonable thing to log, I believe). If you > > > actually require it to be set to "all", most people won't have any use at > > > all for it... > > > > That's a reasonable feature request - but imo it's a separate > > one. It seems pretty noncontroversial and simple to make > > log_statement=all log replication commands. What you want - and you're > > sure not alone with that - is something considerably more complex... > > > > > I'm just saying if we're going to do it, let's do it right from the > beginning. Your wish just seems like a separate feature to me. Including replication commands in 'all' seems correct independent of the desire for a more granular control. > Or are you suggesting this would be something we'd backpatch? Thought about it for a sec, and then decided it doesn't seem warranted. Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services
В списке pgsql-hackers по дате отправления: