Hi!
Thank you.
As Laurentz said, even if you set it to 5TB, no WAL files older than
the files needed by the last checkpoint don't remain. If you don't
need a hot-standby, you can use pg_receivewal to save WAL files on the
"standby" server. If you need the hot-standby, WAL files should be
At Mon, 18 May 2020 11:11:44 +0300, "Andrus" wrote in
> Hi!
>
> >This is confused or at least confusing.
> >- "max_wal_size" of 5TB is clearly insane.
As Laurentz said, even if you set it to 5TB, no WAL files older than
the files needed by the last checkpoint don't remain. If you don't
need a
Hi!
This is confused or at least confusing.
- "max_wal_size" of 5TB is clearly insane.
- I don't understand what you mean by "Start backup server for hot standby
backups".
Do I get it right that you want to copy a streaming replication standby
server's data
directory to perform PITR?
I want
On Sun, 2020-05-17 at 17:41 +0300, Andrus wrote:
> How to implement hot standby and PITR recovery possibility in same backup
> server.
>
> Plan is:
>
> 1. Create base backup using
>
> pg_basebackup --checkpoint=fast --verbose --progress --write-recovery-conf -D
>
Hi!
How to implement hot standby and PITR recovery possibility in same backup
server.
Plan is:
1. Create base backup using
pg_basebackup --checkpoint=fast --verbose --progress --write-recovery-conf -D
/var/lib/postgresql/12/standby
2. Create backup copy of /var/lib/postgresql/12/standby
