| From: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
|---|---|
| To: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Unable to start postgresql-14 |
| Date: | 2023-12-24 16:28:02 |
| Message-ID: | CANzqJaCgpPtteYUKKc=fWj6w-grEk=zqX6vedcObh44U0CbeaQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sun, Dec 24, 2023 at 11:04 AM Johnathan Tiamoh <johnathantiamoh(at)gmail(dot)com>
wrote:
>
> If so how was the backup done?
> It was taken with a customized script that uses pg_dump.
>
That's your problem: pg_dump is a logical backup. All the WAL records are
now completely invalid.
If you want PITR, read
https://www.postgresql.org/docs/current/continuous-archiving.html *and then
use a dedicated PITR program*.like (alphabetically) barman or pgbackrest.
I like pgbackrest. It's always worked for me, and the developers respond
quickly to issues raised on github. Stephen also monitors this list.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter J. Holzer | 2023-12-24 21:43:32 | Re: Changing a schema's name with function1 calling function2 |
| Previous Message | Adrian Klaver | 2023-12-24 16:27:21 | Re: Unable to start postgresql-14 |