Re: race condition when writing pg_control
Thomas Munro <thomas.munro@gmail.com>
From: Thomas Munro <thomas.munro@gmail.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: "Bossart, Nathan" <bossartn@amazon.com>,
Fujii Masao <masao.fujii@oss.nttdata.com>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2020-06-08T02:48:55Z
Lists: pgsql-hackers
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?
Commits
-
Fix locking bugs that could corrupt pg_control.
- 09dc17486393 9.5.23 landed
- 644cac32a0bc 9.6.19 landed
- fd11b842eba9 10.14 landed
- 48eb6a3c895d 11.9 landed
- 72766ad6397a 12.4 landed
- acefa2cca6a2 13.0 landed
- 57cb8063089a 14.0 landed