Re: pg_replication_origin_drop API potential race condition
Amit Kapila <amit.kapila16@gmail.com>
From: Amit Kapila <amit.kapila16@gmail.com>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Petr Jelinek <pjmodos@pjmodos.net>, Euler Taveira <euler@eulerto.com>, Peter Smith <smithpb2250@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2021-02-10T02:33:58Z
Lists: pgsql-hackers
On Tue, Feb 9, 2021 at 5:53 PM Alvaro Herrera <alvherre@alvh.no-ip.org> wrote: > > On 2021-Feb-09, Amit Kapila wrote: > > > On Tue, Feb 9, 2021 at 4:16 PM Alvaro Herrera <alvherre@alvh.no-ip.org> wrote: > > > > By all means let's get the bug fixed. > > > > I am planning to push this in HEAD only as there is no user reported > > problem and this is actually more about giving correct information to > > the user rather than some misleading message. Do you see any need to > > back-patch this change? > > master-only sounds OK. > Pushed! -- With Regards, Amit Kapila.
Commits
-
Make pg_replication_origin_drop safe against concurrent drops.
- cd142e032ebd 14.0 landed