Re: More race conditions in logical replication
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Petr Jelinek <petr.jelinek@2ndquadrant.com>, Tom Lane <tgl@sss.pgh.pa.us>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>, Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Date: 2017-07-25T18:29:50Z
Lists: pgsql-hackers
On Tue, Jul 25, 2017 at 1:42 PM, Alvaro Herrera <alvherre@2ndquadrant.com> wrote: > As I see it, we need to backpatch at least parts of this patch. I've > received reports that in earlier branches pglogical and BDR can > sometimes leave slots behind when removing nodes, and I have a hunch > that it can be explained by the bugs being fixed here. Now we cannot > use condition variables in back-branches, so we'll need to figure out > how to actually do it ... If all you had to back-patch was the condition variable code itself, that might not really be all that bad, but it depends on the WaitEventSet stuff, which I think is far too dangerous to back-patch. However, you might be able to create a dumber, slower version that only uses WaitLatch. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Commits
-
Fix vertical spanning in table "wait_event Description".
- e88928c50dfe 10.0 landed
-
Fix replication origin-related race conditions
- b2c95a3798ff 10.0 landed
-
Fix inadequacies in recently added wait events
- 030273b7ea46 10.0 landed
-
Fix race conditions in replication slot operations
- 9915de6c1cb2 10.0 landed