| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Koen De Groote <kdg(dot)dev(at)gmail(dot)com> |
| Cc: | PostgreSQL General <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Postgres restore sometimes restores to a point 2 days in the past |
| Date: | 2025-01-31 22:26:56 |
| Message-ID: | a49edff0-f8d8-44c1-9921-ef815f8a1d2a@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 1/31/25 13:52, Koen De Groote wrote:
> > I should have asked earlier what is the archive command
>
> The example from the documentation, but with GZIP. So from the
> documentation:
> https://www.postgresql.org/docs/16/continuous-archiving.html#BACKUP-ARCHIVING-WAL <https://www.postgresql.org/docs/16/continuous-archiving.html#BACKUP-ARCHIVING-WAL>
>
> Which becomes this: archive_command = 'test ! -f
> /mnt/server/archivedir/%f.gz && gzip -c %p /mnt/server/archivedir/%f.gz'
>
>
> > Are you setting standby.signal or recovery.signal or both
>
> Sorry, I keep confusing them. I checked my deployment code, it's
> recovery.signal and only that.
Do you have any of the Recovery Target settings from below set?:
https://www.postgresql.org/docs/current/runtime-config-wal.html#RUNTIME-CONFIG-WAL-RECOVERY-TARGET
>
> Regards,
> Koen De Groote
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gabriele Tozzi | 2025-02-01 02:29:49 | Toughs for CREATE DATABASE performance improvement |
| Previous Message | Koen De Groote | 2025-01-31 21:52:39 | Re: Postgres restore sometimes restores to a point 2 days in the past |