Re: potential stuck lock in SaveSlotToPath()

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
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-02 06:21:50
Message-ID: 20200402062150.GB112468@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message movead.li@highgo.ca 2020-04-02 06:26:08 Re: A bug when use get_bit() function for a long bytea string
Previous Message Michael Paquier 2020-04-02 06:14:21 Re: ALTER tbl rewrite loses CLUSTER ON index