From 31176cd686f31dcb71392f6583f7b8d9cef63770 Mon Sep 17 00:00:00 2001
From: Daniel Baumann pg_rewind — synchronize a PostgreSQL data directory with another data directory that was forked from it
+ pg_rewind — synchronize a PostgreSQL data directory with another data directory that was forked from it
pg_rewind is a tool for synchronizing a PostgreSQL cluster
with another copy of the same cluster, after the clusters' timelines have
diverged. A typical scenario is to bring an old primary server back online
@@ -192,8 +192,9 @@ GRANT EXECUTE ON function pg_catalog.pg_read_binary_file(text, bigint, bigint, b
Create a pg_rewind
Synopsis
pg_rewind
[option
...] { -D
| --target-pgdata
} directory
{ --source-pgdata=
| directory
--source-server=
} connstr
Description
pg_rewind
Synopsis
pg_rewind
[option
...] { -D
| --target-pgdata
} directory
{ --source-pgdata=
| directory
--source-server=
} connstr
Description
backup_label
,
tablespace_map
,
pg_internal.init
,
- postmaster.opts
, and
- postmaster.pid
, as well as any file or directory
+ postmaster.opts
,
+ postmaster.pid
and
+ .DS_Store
as well as any file or directory
beginning with pgsql_tmp
, are omitted.
backup_label
file to begin WAL replay at
@@ -206,4 +207,4 @@ GRANT EXECUTE ON function pg_catalog.pg_read_binary_file(text, bigint, bigint, b
When starting the target, PostgreSQL replays
all the required WAL, resulting in a data directory in a consistent
state.
-