Re: potential stuck lock in SaveSlotToPath()
Alvaro Herrera <alvherre@2ndquadrant.com>
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>, Robert Haas <robertmhaas@gmail.com>, Andres Freund <andres@anarazel.de>
Date: 2020-03-25T13:41:13Z
Lists: pgsql-hackers
On 2020-Mar-25, Peter Eisentraut wrote: > On 2020-03-20 16:38, Robert Haas wrote: > > On Fri, Mar 20, 2020 at 11:32 AM Peter Eisentraut > > <peter.eisentraut@2ndquadrant.com> wrote: > > > On 2020-03-19 16:38, Robert Haas wrote: > > > > Incidentally, the wait-event handling in SaveSlotToPath() doesn't look > > > > right for the early-exit cases either. > > > > > > There appear to be appropriate pgstat_report_wait_end() calls. What are > > > you seeing? > > > > Oh, you're right. I think I got confused because the rename() and > > close() don't have that, but those don't have a wait event set either. > > Sorry for the noise. > > Any concerns about applying and backpatching the patch I posted? It looks a straight bug fix to me, I agree it should be back-patched. > The talk about reorganizing this code doesn't seem very concrete at the > moment and would probably not be backpatch material anyway. Agreed on both counts. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Commits
-
Drop slot's LWLock before returning from SaveSlotToPath()
- ce28a43ffa89 9.5.22 landed
- 2d8597ba66a1 9.6.18 landed
- f36a10434a31 10.13 landed
- ba4cc05ce22d 11.8 landed
- 223e9c77dcaf 12.3 landed
- 49bf81536e24 13.0 landed