Re: pg_replication_origin_drop API potential race condition
От | Amit Kapila |
---|---|
Тема | Re: pg_replication_origin_drop API potential race condition |
Дата | |
Msg-id | CAA4eK1KZG63qUYK-F45zs9bHeZpCEB+bjewcGPkBt-LeF-91WA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: pg_replication_origin_drop API potential race condition (Peter Smith <smithpb2250@gmail.com>) |
Ответы |
Re: pg_replication_origin_drop API potential race condition
|
Список | pgsql-hackers |
On Thu, Feb 4, 2021 at 9:57 AM Peter Smith <smithpb2250@gmail.com> wrote: > > On Wed, Feb 3, 2021 at 11:17 PM Amit Kapila <amit.kapila16@gmail.com> wrote: > > > > > How about if we call replorigin_by_name() inside replorigin_drop after > > acquiring the lock? Wouldn't that close this race condition? We are > > doing something similar for pg_replication_origin_advance(). > > > > Yes, that seems ok. > > I wonder if it is better to isolate that locked portion > (replyorigin_by_name + replorigin_drop) so that in addition to being > called from pg_replication_origin_drop, we can call it internally from > PG code to safely drop the origins. > Yeah, I think that would be really good. -- With Regards, Amit Kapila.
В списке pgsql-hackers по дате отправления: