Re: potential stuck lock in SaveSlotToPath()

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Subject: Re: potential stuck lock in SaveSlotToPath()
Date: 2020-04-05 08:13:44
Message-ID: 309c35bf-4279-2303-4db6-3b6ae8e5adf0@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2020-04-02 08:21, Michael Paquier wrote:
> On Wed, Apr 01, 2020 at 04:26:25PM +0200, Peter Eisentraut wrote:
>> Good catch. How about the attached patch?
>
> WFM. Another trick would be to call LWLockRelease() after generating
> the log, but I find your patch more consistent with the surroundings.

done

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jaime Casanova 2020-04-05 08:18:50 segmentation fault using currtid and partitioned tables
Previous Message Fabien COELHO 2020-04-05 07:38:17 Re: Add A Glossary