Re: pgsql: Fix pg_basebackup with in-place tablespaces.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: David Steele <david(at)pgmasters(dot)net>
Cc: Thomas Munro <tmunro(at)postgresql(dot)org>, pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Fix pg_basebackup with in-place tablespaces.
Date: 2022-03-15 21:28:23
Message-ID: 428075.1647379703@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

David Steele <david(at)pgmasters(dot)net> writes:
> On 3/14/22 19:31, Thomas Munro wrote:
>> Fix pg_basebackup with in-place tablespaces.

> Perhaps I'm being picky, but seems like this logic should be wrapped in:
> if (allow_in_place_tablespaces)
> {
> <...>
> }
> I worry about strange effects when this GUC is not enabled.

What would happen if someone created an in-place tablespace and
then turned off the GUC?

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Thomas Munro 2022-03-15 22:13:53 Re: pgsql: Fix pg_basebackup with in-place tablespaces.
Previous Message David Steele 2022-03-15 20:40:35 Re: pgsql: Fix pg_basebackup with in-place tablespaces.