Re: Logical decoding on standby

From: Andres Freund <andres(at)anarazel(dot)de>
To: Craig Ringer <craig(at)2ndquadrant(dot)com>
Cc: Simon Riggs <simon(dot)riggs(at)2ndquadrant(dot)com>, Thom Brown <thom(at)linux(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Logical decoding on standby
Date: 2017-03-30 17:16:53
Message-ID: 20170330171652.ra7wdvkuniiuggxj@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2017-03-29 08:01:34 +0800, Craig Ringer wrote:
> On 28 March 2017 at 23:22, Andres Freund <andres(at)anarazel(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dmitry Dolgov 2017-03-30 17:18:46 Re: [PATCH] Generic type subscripting
Previous Message Andres Freund 2017-03-30 17:16:07 Re: Logical decoding on standby