From: Ronan Dunklau <ronan.dunklau@aiven.io>
To: Ibrar Ahmed <ibrar.ahmad@gmail.com>
To: Amit Khandekar <amitdkhan.pg@gmail.com>
To: pgsql-hackers@lists.postgresql.org, "Drouvot, Bertrand" <bdrouvot@amazon.com>
Cc: Andres Freund <andres@anarazel.de>
Cc: fabriziomello@gmail.com, Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: tushar <tushar.ahuja@enterprisedb.com>
Cc: [pgdg] Robert Haas <robertmhaas@gmail.com>
Cc: Rahila Syed <rahila.syed@2ndquadrant.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: Minimal logical decoding on standbys
Date: Mon, 02 Aug 2021 17:47:14 +0200
Message-ID: <7574277.rk4qtukel5@aivenronan> (raw)
In-Reply-To: <c275aaa7-5c57-eda2-5b70-a6774e9bc13b@amazon.com>
References: <CAFcNs+q9FvSW7gMqM__aeWOoDNqfcQCoB8LiO-X33fvqGO8mkQ@mail.gmail.com>
<1655255.DiLJNMXF8A@aivenronan>
<c275aaa7-5c57-eda2-5b70-a6774e9bc13b@amazon.com>
Le lundi 2 août 2021, 17:31:46 CEST Drouvot, Bertrand a écrit :
> > I think the beahviour when dropping a database on the primary should be
> > documented, and proper procedures for handling it correctly should be
> > suggested.
> >
> > Something along the lines of:
> >
> > "If a database is dropped on the primary server, the logical replication
> > slot on the standby will be dropped as well. This means that you should
> > ensure that the client usually connected to this slot has had the
> > opportunity to stream the latest changes before the database is dropped."
>
> I am not sure we should highlight this as part of this patch.
>
> I mean, the same would currently occur on a non standby if you drop a
> database that has a replication slot linked to it.
The way I see it, the main difference is that you drop an additional object on
the standby, which doesn't exist and that you don't necessarily have any
knowledge of on the primary. As such, I thought it would be better to be
explicit about it to warn users of that possible case.
Regards,
--
Ronan Dunklau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: ronan.dunklau@aiven.io, ibrar.ahmad@gmail.com, amitdkhan.pg@gmail.com, bdrouvot@amazon.com, andres@anarazel.de, alvherre@2ndquadrant.com, tushar.ahuja@enterprisedb.com, robertmhaas@gmail.com, rahila.syed@2ndquadrant.com
Subject: Re: Minimal logical decoding on standbys
In-Reply-To: <7574277.rk4qtukel5@aivenronan>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox