Re: Assertion failure in SnapBuildInitialSnapshot()
От | Amit Kapila |
---|---|
Тема | Re: Assertion failure in SnapBuildInitialSnapshot() |
Дата | |
Msg-id | CAA4eK1+UArMy1hE32CMaVkVaD51MNJMeH5oEXc72O--ouh4gDA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Assertion failure in SnapBuildInitialSnapshot() (Masahiko Sawada <sawada.mshk@gmail.com>) |
Ответы |
Re: Assertion failure in SnapBuildInitialSnapshot()
|
Список | pgsql-hackers |
On Tue, Jan 31, 2023 at 11:12 AM Masahiko Sawada <sawada.mshk@gmail.com> wrote: > > On Mon, Jan 30, 2023 at 9:41 PM Masahiko Sawada <sawada.mshk@gmail.com> wrote: > > I've attached patches for HEAD and backbranches. Please review them. > Shall we add a comment like the one below in ReplicationSlotsComputeRequiredXmin()? diff --git a/src/backend/replication/slot.c b/src/backend/replication/slot.c index f286918f69..e28d48bca7 100644 --- a/src/backend/replication/slot.c +++ b/src/backend/replication/slot.c @@ -840,6 +840,13 @@ ReplicationSlotsComputeRequiredXmin(bool already_locked) Assert(ReplicationSlotCtl != NULL); + /* + * It is possible that by the time we compute the agg_xmin here and before + * updating replication_slot_xmin, the CreateInitDecodingContext() will + * compute and update replication_slot_xmin. So, we need to acquire + * ProcArrayLock here to avoid retreating the value of replication_slot_xmin. + */ + -- With Regards, Amit Kapila.
В списке pgsql-hackers по дате отправления: