Re: allow_in_place_tablespaces vs. pg_basebackup

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: allow_in_place_tablespaces vs. pg_basebackup
Date: 2023-04-17 05:30:19
Message-ID: ZDzZawDdBWVmXoD/@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Apr 14, 2023 at 04:11:47PM -0400, Robert Haas wrote:
> Do people think it's OK to do that now, or should I wait until we've
> branched? I personally think this is bug-fix-ish enough that now is
> OK, but I'll certainly forebear if others disagree.

FWIW, doing that now rather than the beginning of July is OK for me
for this stuff.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Mikael Kjellström 2023-04-17 05:44:36 Re: Direct I/O
Previous Message Nishant Sharma 2023-04-17 05:30:05 Re: postgres_fdw: wrong results with self join + enable_nestloop off