Postgres Pro
Downloads
Home   >   mailing lists

Re: race condition when writing pg_control - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: race condition when writing pg_control
Date
Msg-id CA+hUKGKToqjdeRtr8ZHVbPToShun5ifjioj6x3nsjseOkhCMEQ@mail.gmail.com
Whole thread Raw
In response to Re: race condition when writing pg_control  (Michael Paquier <michael@paquier.xyz>)
Responses Re: race condition when writing pg_control  ("Bossart, Nathan" <bossartn@amazon.com>)
List pgsql-hackers
Tree view 
On Wed, Jun 3, 2020 at 2:03 PM Michael Paquier <michael@paquier.xyz> wrote:
> On Wed, Jun 03, 2020 at 10:56:13AM +1200, Thomas Munro wrote:
> > Sorry for my radio silence, I got tangled up with a couple of
> > conferences.  I'm planning to look at 0001 and 0002 shortly.
>
> Thanks!

I pushed 0001 and 0002, squashed into one commit.  I'm not sure about
0003.  If we're going to do that, wouldn't it be better to just
acquire the lock in that one extra place in StartupXLOG(), rather than
introducing the extra parameter?

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: SIGSEGV from START_REPLICATION 0/XXXXXXX in XLogSendPhysical ()at walsender.c:2762
Next
From: "Bossart, Nathan"
Date:
Subject: Re: race condition when writing pg_control