Re: allow_in_place_tablespaces vs. pg_basebackup

Robert Haas <robertmhaas@gmail.com>

From: Robert Haas <robertmhaas@gmail.com>

To: Michael Paquier <michael@paquier.xyz>

Cc: Thomas Munro <thomas.munro@gmail.com>, Kyotaro Horiguchi <horikyota.ntt@gmail.com>, pgsql-hackers@postgresql.org

Date: 2023-04-18T15:35:41Z

Lists: pgsql-hackers

On Mon, Apr 17, 2023 at 1:30 AM Michael Paquier <michael@paquier.xyz> wrote:
> FWIW, doing that now rather than the beginning of July is OK for me
> for this stuff.

OK, committed.

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

Commits

Fix pg_basebackup with in-place tablespaces some more.
- 363e8f911546 16.0 landed
Fix pg_basebackup with in-place tablespaces.
- c6f2f01611d4 15.0 cited
Allow "in place" tablespaces.
- 7170f2159fb2 15.0 cited
Avoid including tablespaces inside PGDATA twice in base backups
- b168c5ef2730 9.4.0 cited
Tablespaces. Alternate database locations are dead, long live tablespaces.
- 2467394ee156 8.0.0 cited