Horton

Re: allow_in_place_tablespaces vs. pg_basebackup

Michael Paquier <michael@paquier.xyz>

View thread View on postgr.es
From: Michael Paquier <michael@paquier.xyz>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Thomas Munro <thomas.munro@gmail.com>, Kyotaro Horiguchi <horikyota.ntt@gmail.com>, pgsql-hackers@postgresql.org
Date: 2023-03-21T23:59:19Z
Lists: pgsql-hackers 
On Mon, Mar 20, 2023 at 07:56:42AM -0400, Robert Haas wrote:
> Anyone want to comment on this?

I have not checked the patch in details, but perhaps this needs at
least one test?
--
Michael

Commits

  1. Fix pg_basebackup with in-place tablespaces some more.

  2. Fix pg_basebackup with in-place tablespaces.

  3. Allow "in place" tablespaces.

  4. Avoid including tablespaces inside PGDATA twice in base backups

  5. Tablespaces. Alternate database locations are dead, long live tablespaces.