Re: [PATCH] Race condition in logical walsender causes long postgresql shutdown delay
Alvaro Herrera <alvherre@2ndquadrant.com>
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Jeff Janes <jeff.janes@gmail.com>
Cc: Craig Ringer <craig@2ndquadrant.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2019-09-27T01:22:13Z
Lists: pgsql-hackers
On 2019-Sep-26, Jeff Janes wrote: > On Wed, Sep 11, 2019 at 3:52 PM Alvaro Herrera <alvherre@2ndquadrant.com> > wrote: > > > Reading over this code, I noticed that the detection of the catch-up > > state ends up being duplicate code, so I would rework that function as > > in the attached patch. > > > > The naming of those flags (got_SIGUSR2, got_STOPPING) is terrible, but > > I'm not going to change that in a backpatchable bug fix. > > Hi Alvaro, does this count as a review? Well, I'm already a second pair of eyes for Craig's code, so I think it does :-) I would have liked confirmation from Craig that my change looks okay to him too, but maybe we'll have to go without that. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Commits
-
Fix minor bug in logical-replication walsender shutdown
- 38ddeab13b4b 13.0 landed
- 1391c13ce3b8 12.1 landed
- b2ab06e0251a 9.5.20 landed
- abd5071d2163 9.4.25 landed
- 5f038991ecf9 9.6.16 landed
- 45e4067c05b1 11.6 landed
- 0d9fcbada992 10.11 landed
-
Prevent possibility of panics during shutdown checkpoint.
- c6c333436491 10.0 cited