diff options
| author | Michael Paquier <michael@paquier.xyz> | 2019-04-05 10:37:59 +0900 |
|---|---|---|
| committer | Michael Paquier <michael@paquier.xyz> | 2019-04-05 10:37:59 +0900 |
| commit | bfc80683ce51590545350b2c8ccfaa9e7a2a1870 (patch) | |
| tree | 472eccd4b166a100ffa3b2946ab44ab5c522f525 /src/interfaces/libpq/fe-secure-gssapi.c | |
| parent | 57a7a3adfe4eadb471bb45a7effb1a99ebb00a7b (diff) | |
| download | postgresql-bfc80683ce51590545350b2c8ccfaa9e7a2a1870.tar.gz postgresql-bfc80683ce51590545350b2c8ccfaa9e7a2a1870.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/interfaces/libpq/fe-secure-gssapi.c')
0 files changed, 0 insertions, 0 deletions