-
Notifications
You must be signed in to change notification settings - Fork 86
"pg_probackup-15 archive-get" ignores archived wals while recovering to latest state #621
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
At 2024-05-29 12:44 standby instance have been promoted to primary :
Do we have any chances to apply later wals after this occasion ? |
Looks like it is pg_probackup archive-get problem. I copied all needed wals manually to server local dir and setted up restore by cp :
And now its recovered forward after 0000000B0000000000000037 without any problems:
So, my test case :
|
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Hi guys ! I'm testing wal archive recovery and cant to understand why archive-get just lose some last wals :
postgresql.auto.conf:
wals in pg_probackup archive :
postgresql.log while recovery :
Why it is ended on 0000000A0000000000000037 last completed transaction was at log time 2024-05-29 12:44:00.017459+05 ??
Where is
-rw-------. 1 postgres postgres 79741 May 29 13:18 0000000B0000000000000038.gz
-rw-------. 1 postgres postgres 83013 May 29 13:25 0000000B0000000000000039.gz
etc.... ???
The text was updated successfully, but these errors were encountered: