On 2017-03-29 08:01:34 +0800, Craig Ringer wrote: > On 28 March 2017 at 23:22, Andres Freund <and...@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 don't think that's really comparable, because the other things aren't global objects, which replication slots are. - Andres -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
