Re: potential stuck lock in SaveSlotToPath() - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: potential stuck lock in SaveSlotToPath()
Date
Msg-id 5ffa6f6d-cadd-64a9-5ab6-4362fb20ae93@2ndquadrant.com
Whole thread Raw
In response to Re: potential stuck lock in SaveSlotToPath()  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: potential stuck lock in SaveSlotToPath()  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Re: potential stuck lock in SaveSlotToPath()  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
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?

The talk about reorganizing this code doesn't seem very concrete at the 
moment and would probably not be backpatch material anyway.


-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Justin Pryzby
Date:
Subject: Re: error context for vacuum to include block number
Next
From: John Naylor
Date:
Subject: Re: truncating timestamps on arbitrary intervals