Re: standby recovery fails (tablespace related) (tentative patch and discussion)

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, Julien Rouhaud <rjuju123(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: standby recovery fails (tablespace related) (tentative patch and discussion)
Date: 2022-03-29 13:31:42
Message-ID: CA+TgmoY1rUjA+RaRug791YAtNgNeNxXtEC8ytig6LNHa9_FTug@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Mar 29, 2022 at 9:28 AM Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
> OK, this is a bug that's been open for years. A fix can be committed
> after the feature freeze anyway.

+1

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2022-03-29 13:38:29 Re: Add parameter jit_warn_above_fraction
Previous Message Robert Haas 2022-03-29 13:30:36 Re: Accommodate startup process in a separate ProcState array slot instead of in MaxBackends slots.