On Sun, Dec 24, 2023 at 11:04 AM Johnathan Tiamoh
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
On 12/24/23 08:03, Johnathan Tiamoh wrote:
Was this backup taken before the data directory was deleted?
Yes. I restored it from a 1-day old backup, but unfortunately, I
couldn't apply the logs.
If the backup was done using pg_dump as mentioned below why where you
applying logs?
You need
Was this backup taken before the data directory was deleted?
Yes. I restored it from a 1-day old backup, but unfortunately, I couldn't
apply the logs.
If so how was the backup done?
It was taken with a customized script that uses pg_dump.
Does this mean you recreated the data directory from
On 12/23/23 10:05, Johnathan Tiamoh wrote:
More information needed:
1) Exact Postgres version e.g 14.x
Postgresql Version 14. 10
2) Is it community version or fork?
Community version
3) What was the command you used to start the cluster?
systemctl start postgresql-14
4) Do you have
More information needed:
1) Exact Postgres version e.g 14.x
Postgresql Version 14. 10
2) Is it community version or fork?
Community version
3) What was the command you used to start the cluster?
systemctl start postgresql-14
4) Do you have replication/WAL archiving set up?
Yes.
Just to
On 12/22/23 22:48, Johnathan Tiamoh wrote:
Hello,
I am able to start postgresql because of the below error. Please is
there any help
User
You
FATAL: xlog flush request 4392/164662F8 is not satisfied --- flushed
only to 4392/F58
UserYouFATAL: xlog flush request 4392/164662F8 is not
Hello,
I am able to start postgresql because of the below error. Please is there
any help
[image: User]
You
FATAL: xlog flush request 4392/164662F8 is not satisfied --- flushed only
to 4392/F58
[image: User]YouFATAL: xlog flush request 4392/164662F8 is not satisfied
--- flushed only to
