pgsql: Change the way pg_basebackup's tablespace mapping is implemented - Mailing list pgsql-committers

From Heikki Linnakangas
Subject pgsql: Change the way pg_basebackup's tablespace mapping is implemented
Date
Msg-id E1XKjJF-0007iv-HL@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Change the way pg_basebackup's tablespace mapping is implemented.

Previously, we would first create the symlinks the way they are in the
original system, and at the end replace them with the mapped symlinks.
That never really made much sense, so now we create the symlink pointing
to the correct location to begin with, so that there's no need to fix
them at the end.

The old coding didn't work correctly on Windows, because Windows junction
points look more like directories than files, and ought to be removed with
rmdir rather than unlink. Also, it incorrectly used "%d" rather than "%u"
to print an Oid, but that's gone now.

Report and patch by Amit Kapila, with minor changes by me. Reviewed by
MauMau. Backpatch to 9.4, where the --tablespace feature was added.

Branch
------
REL9_4_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/8a22633f52f2399118d6ad3c2c4da6a31f07e907

Modified Files
--------------
src/bin/pg_basebackup/pg_basebackup.c |   64 +++++++++++----------------------
1 file changed, 20 insertions(+), 44 deletions(-)


pgsql-committers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: pgsql: Change the way pg_basebackup's tablespace mapping is implemented
Next
From: Heikki Linnakangas
Date:
Subject: pgsql: Fix comment in pg_basebackup.