On 2020/10/08 7:12, Jeff Janes wrote:
On Wed, Oct 7, 2020 at 5:47 PM David G. Johnston mailto:david.g.johns...@gmail.com>> wrote:
On Wed, Oct 7, 2020 at 2:35 PM Jeff Janes mailto:jeff.ja...@gmail.com>> wrote:
Quoting the docs:
https://www.postgresql.org/docs/13/continuou
On Wed, Oct 7, 2020 at 5:47 PM David G. Johnston
wrote:
> On Wed, Oct 7, 2020 at 2:35 PM Jeff Janes wrote:
>
>> Quoting the docs:
>>
>> https://www.postgresql.org/docs/13/continuous-archiving.html
>>
>> "As with base backups, the easiest way to produce a standalone hot backup
>> is to use the pg
On Wed, Oct 7, 2020 at 2:35 PM Jeff Janes wrote:
> Quoting the docs:
>
> https://www.postgresql.org/docs/13/continuous-archiving.html
>
> "As with base backups, the easiest way to produce a standalone hot backup
> is to use the pg_basebackup tool. If you include the -X parameter when
> calling it
Quoting the docs:
https://www.postgresql.org/docs/13/continuous-archiving.html
"As with base backups, the easiest way to produce a standalone hot backup
is to use the pg_basebackup tool. If you include the -X parameter when
calling it, all the write-ahead log required to use the backup will be
in
