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

From Robert Haas
Subject Re: potential stuck lock in SaveSlotToPath()
Date
Msg-id CA+TgmoatJ6ieLi9HV7Pxv=Bq98oRnp1_6dOoo8Spcw8jfakkag@mail.gmail.com
Whole thread Raw
In response to Re: potential stuck lock in SaveSlotToPath()  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: potential stuck lock in SaveSlotToPath()  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
On Wed, Mar 25, 2020 at 6:13 AM Peter Eisentraut
<peter.eisentraut@2ndquadrant.com> wrote:
> Any concerns about applying and backpatching the patch I posted?

Not from me.

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

+1.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: backup manifests
Next
From: Tom Lane
Date:
Subject: Re: [PATCH] Check operator when creating unique index on partition table