From: | Filip Sedlák <filip(at)sedlakovi(dot)org> |
---|---|
To: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: How to Straming replication chatch up from archive |
Date: | 2023-12-14 07:53:33 |
Message-ID: | 188cbb21-7278-4d2a-ae41-f6bc6bd67aca@sedlakovi.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> if the master overwrite the wal BEFORE they are sent to the standby via
> replication, does the standby *automatically* start looking in WAL
> archive destination?
> Or this step have to be made by hand?
I understand it works this way: normally, the replica tries to stream
from master. If it is not able to (for example, the requested WAL has
been already rotated), then it tries to call the restore_command.
See
https://www.postgresql.org/docs/current/continuous-archiving.html#BACKUP-PITR-RECOVERY
So you just need to specify where the older WALs are. For example
restore_command = 'cp /mnt/nfs/archivedir/%f %p'
assuming the server has a similar archive_command that stores WALs into
that directory.
--
Filip Sedlák
From | Date | Subject | |
---|---|---|---|
Next Message | Sean Flaherty | 2023-12-14 14:48:08 | Re: Increased storage size of jsonb in pg15 |
Previous Message | Ron Johnson | 2023-12-14 02:38:52 | vacuumdb did not analyze all tables?= |