Re: This is too implicit that recovery.signal will be removed
От | Eugen Konkov |
---|---|
Тема | Re: This is too implicit that recovery.signal will be removed |
Дата | |
Msg-id | CAAwmOLw+ju=Y2osBboP37scx=znPF9JusjqOzUcWNmuENWmKvQ@mail.gmail.com обсуждение исходный текст |
Ответ на | This is too implicit that recovery.signal will be removed (PG Doc comments form <noreply@postgresql.org>) |
Список | pgsql-docs |
Only here I found explicit mention that recovery.signal will be removed: https://www.postgresql.org/docs/16/continuous-archiving.html#BACKUP-PITR-RECOVERY see p8. On Thu, Oct 5, 2023 at 10:06 AM PG Doc comments form <noreply@postgresql.org> wrote: > > 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.
В списке pgsql-docs по дате отправления: