diff options
| author | Andrew Dunstan | 2015-05-12 13:29:10 +0000 |
|---|---|---|
| committer | Andrew Dunstan | 2015-05-12 13:29:10 +0000 |
| commit | 72d422a5227ef6f76f412486a395aba9f53bf3f0 (patch) | |
| tree | c94ffeef53c5e4a4ce0c4b055a8256ee6af3b947 /src/backend/replication/repl_scanner.l | |
| parent | d02f16470f117db3038dbfd87662d5f0eb5a2a9b (diff) | |
Map basebackup tablespaces using a tablespace_map file
Windows can't reliably restore symbolic links from a tar format, so
instead during backup start we create a tablespace_map file, which is
used by the restoring postgres to create the correct links in pg_tblspc.
The backup protocol also now has an option to request this file to be
included in the backup stream, and this is used by pg_basebackup when
operating in tar mode.
This is done on all platforms, not just Windows.
This means that pg_basebackup will not not work in tar mode against 9.4
and older servers, as this protocol option isn't implemented there.
Amit Kapila, reviewed by Dilip Kumar, with a little editing from me.
Diffstat (limited to 'src/backend/replication/repl_scanner.l')
| -rw-r--r-- | src/backend/replication/repl_scanner.l | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/src/backend/replication/repl_scanner.l b/src/backend/replication/repl_scanner.l index f8acb66552c..056cc141293 100644 --- a/src/backend/replication/repl_scanner.l +++ b/src/backend/replication/repl_scanner.l @@ -88,6 +88,7 @@ NOWAIT { return K_NOWAIT; } PROGRESS { return K_PROGRESS; } MAX_RATE { return K_MAX_RATE; } WAL { return K_WAL; } +TABLESPACE_MAP { return K_TABLESPACE_MAP; } TIMELINE { return K_TIMELINE; } START_REPLICATION { return K_START_REPLICATION; } CREATE_REPLICATION_SLOT { return K_CREATE_REPLICATION_SLOT; } |