On Thu, Oct 5, 2023, 11:11 PG Doc comments form
wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/16/continuous-archiving.html
> Description:
>
> Hello.
>
> On page:
>
> https://www.postgresql.org/docs/current/continuous-archivi
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/16/continuous-archiving.html
Description:
Hello.
On page:
https://www.postgresql.org/docs/current/continuous-archiving.html#BACKUP-PITR-RECOVERY
Is is not clear should I do additional action
On Wed, Oct 4, 2023 at 6:37 PM Erik Wienhold wrote:
> On 2023-10-04 16:24 +0200, PG Doc comments form write:
> > The following documentation comment has been logged on the website:
> >
> > Page: https://www.postgresql.org/docs/16/queries-order.html
> > Description:
> >
> > The document only says
On Thu, Oct 5, 2023 at 8:15 AM PG Doc comments form
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-wa
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
wrote:
>
> The following documentation comment has been logged on the website:
>
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 fil