From 5adafaf176d09ba5ea11ae128416fc5211469bc0 Mon Sep 17 00:00:00 2001 From: Alvaro Herrera Date: Fri, 27 Sep 2019 16:40:01 -0300 Subject: Have pg_rewind run crash recovery before rewinding MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit If we don't do this, the rewind fails if the server wasn't cleanly shut down, which seems unhelpful serving no purpose. Also provide a new option --no-ensure-shutdown to suppress this behavior, for alleged advanced usage that prefers to avoid the crash recovery. Authors: Paul Guo, Jimmy Yih, Ashwin Agrawal Reviewed-by: Álvaro Herrera Discussion: https://postgr.es/m/CAEET0ZEffUkXc48pg2iqARQgGRYDiiVxDu+yYek_bTwJF+q=Uw@mail.gmail.com --- doc/src/sgml/ref/pg_rewind.sgml | 15 +++++++++++++++ 1 file changed, 15 insertions(+) (limited to 'doc/src') diff --git a/doc/src/sgml/ref/pg_rewind.sgml b/doc/src/sgml/ref/pg_rewind.sgml index ac142d22fcd..a06e5ac5e11 100644 --- a/doc/src/sgml/ref/pg_rewind.sgml +++ b/doc/src/sgml/ref/pg_rewind.sgml @@ -165,6 +165,21 @@ PostgreSQL documentation + + + + + pg_rewind verifies that the target server + is cleanly shutdown before rewinding; by default, if it isn't, it + starts the server in single-user mode to complete crash recovery. + By passing this option, pg_rewind skips + this and errors out immediately if the server is not cleanly shut + down. Users are expected to handle the situation themselves in that + case. + + + + -- cgit v1.2.3