diff options
| author | Michael Paquier <michael@paquier.xyz> | 2019-04-05 10:38:21 +0900 |
|---|---|---|
| committer | Michael Paquier <michael@paquier.xyz> | 2019-04-05 10:38:21 +0900 |
| commit | 064b3fcbdb198f04ee74e01dd48b3d75448b3c4c (patch) | |
| tree | 7b2001d7bb6676fff3ced83092b48bc8d970f933 /src/backend/utils/adt/ruleutils.c | |
| parent | 7dbc0759e0207436851ccc7098250a8110efe655 (diff) | |
| download | postgresql-064b3fcbdb198f04ee74e01dd48b3d75448b3c4c.tar.gz postgresql-064b3fcbdb198f04ee74e01dd48b3d75448b3c4c.zip | |
Fix some documentation in pg_rewind
Since 11, it is possible to use a non-superuser role when using an
online source cluster with pg_rewind as long as the role has proper
permissions to execute on the source all the functions used by
pg_rewind, and the documentation stated that a superuser is necessary.
Let's add at the same time all the details needed to create such a
role.
A second confusion which comes a lot from users is that it is necessary
to issue a checkpoint on a freshly-promoted standby so as its control
file has up-to-date timeline information which is used by pg_rewind to
validate the operation. Let's document that properly. This is
back-patched down to 9.5 where pg_rewind has been introduced.
Author: Michael Paquier
Reviewed-by: Magnus Hagander
Discussion: https://postgr.es/m/CABUevEz5bpvbwVsYCaSMV80CBZ5-82nkMzbb+Bu=h1m=rLdn=g@mail.gmail.com
Backpatch-through: 9.5
Diffstat (limited to 'src/backend/utils/adt/ruleutils.c')
0 files changed, 0 insertions, 0 deletions