Re: potential stuck lock in SaveSlotToPath()

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: 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-03-26 13:16:05
Message-ID: 41073acc-41a3-1602-1216-a979b93ed626@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2020-03-25 17:56, Robert Haas wrote:
> On Wed, Mar 25, 2020 at 6:13 AM Peter Eisentraut
> <peter(dot)eisentraut(at)2ndquadrant(dot)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.

committed and backpatched

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2020-03-26 13:20:37 Re: replay pause vs. standby promotion
Previous Message Fujii Masao 2020-03-26 12:41:34 Re: pg_stat_statements: rows not updated for CREATE TABLE AS SELECT statements