From: | PG Doc comments form <noreply(at)postgresql(dot)org> |
---|---|
To: | pgsql-docs(at)lists(dot)postgresql(dot)org |
Cc: | konkove(at)gmail(dot)com |
Subject: | This is too implicit that recovery.signal will be removed |
Date: | 2023-10-05 14:05:33 |
Message-ID: | 169651473352.657.15892407948633456020@wrigleys.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/16/runtime-config-wal.html
Description:
Hello.
On the page
https://www.postgresql.org/docs/current/runtime-config-wal.html
Actual:
>To start the server in targeted recovery mode, create a file called
recovery.signal in the data directory. If both standby.signal and
recovery.signal files are created, standby mode takes precedence. Targeted
recovery mode ends when the archived WAL is fully replayed, or when
recovery_target is reached. In this mode, the parameters from both this
section and Section 20.5.6 will be used.
Expected:
>To start the server in targeted recovery mode, create a file called
recovery.signal in the data directory. If both standby.signal and
recovery.signal files are created, standby mode takes precedence. Targeted
recovery mode ends and recovery.signal file is removed when the archived WAL
is fully replayed, or when recovery_target is reached. In this mode, the
parameters from both this section and Section 20.5.6 will be used. File
'recovery.signal' is not removed when `recovery_target_action` is
*shutdown*.
Overall I did not find page where I can read about all types of *.signal
files and how to deal with them.
From | Date | Subject | |
---|---|---|---|
Next Message | Eugen Konkov | 2023-10-05 14:52:30 | Re: This is too implicit that recovery.signal will be removed |
Previous Message | Laurenz Albe | 2023-10-05 06:50:24 | Re: unnest multirange, returned order |