Re: allow_in_place_tablespaces vs. pg_basebackup
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Thomas Munro <thomas.munro@gmail.com>
Cc: Kyotaro Horiguchi <horikyota.ntt@gmail.com>, pgsql-hackers@postgresql.org
Date: 2023-03-20T11:56:42Z
Lists: pgsql-hackers
On Thu, Mar 9, 2023 at 4:15 PM Robert Haas <robertmhaas@gmail.com> wrote: > Now that I'm done grumbling, here's a patch. Anyone want to comment on this? -- 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