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

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
Cc: dilipbalaut(at)gmail(dot)com, robertmhaas(at)gmail(dot)com, michael(at)paquier(dot)xyz, rjuju123(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: standby recovery fails (tablespace related) (tentative patch and discussion)
Date: 2022-07-20 16:34:23
Message-ID: 20220720163423.sgskcrslcjkxznel@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2022-Jul-20, Alvaro Herrera wrote:

> On 2022-Jul-20, Alvaro Herrera wrote:
>
> > I also change the use of allow_invalid_pages to
> > allow_in_place_tablespaces. We could add a
> > separate GUC for this, but it seems overengineering.
>
> Oh, but allow_in_place_tablespaces doesn't exist in versions 14 and
> older, so this strategy doesn't really work.

... and get_dirent_type is new in 14, so that'll be one more hurdle.

--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
"Cuando no hay humildad las personas se degradan" (A. Christie)

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2022-07-20 16:34:24 Re: shared-memory based stats collector - v70
Previous Message Jeff Davis 2022-07-20 16:28:37 Re: Logical insert/update/delete WAL records for custom table AMs