Re: Logical decoding on standby
От | Craig Ringer |
---|---|
Тема | Re: Logical decoding on standby |
Дата | |
Msg-id | CAMsr+YGmEkZP1R6mqd544K6xSaWsj7dVCiKKCQ7tOPJ3Ok-U0Q@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Logical decoding on standby (Andres Freund <andres@anarazel.de>) |
Список | pgsql-hackers |
On 28 March 2017 at 23:22, Andres Freund <andres@anarazel.de> wrote: >> --- a/doc/src/sgml/protocol.sgml >> +++ b/doc/src/sgml/protocol.sgml >> @@ -2034,6 +2034,8 @@ The commands accepted in walsender mode are: >> <para> >> Drops a replication slot, freeing any reserved server-side resources. If >> the slot is currently in use by an active connection, this command fails. >> + If the slot is a logical slot that was created in a database other than >> + the database the walsender is connected to, this command fails. >> </para> >> <variablelist> >> <varlistentry> > > Shouldn't the docs in the drop database section about this? DROP DATABASE doesn't really discuss all the resources it drops, but I'm happy to add mention of replication slots handling. I just notice that I failed to remove the docs changes regarding dropping slots becoming db-specific, so I'll post a follow-up for that in a sec. -- Craig Ringer http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services
В списке pgsql-hackers по дате отправления: