Skip to content

catchup incorrectly checks the timeline history in some cases #463

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
kulaginm opened this issue Dec 27, 2021 · 0 comments · Fixed by #462
Closed

catchup incorrectly checks the timeline history in some cases #463

kulaginm opened this issue Dec 27, 2021 · 0 comments · Fixed by #462
Assignees
@kulaginm
Milestone
2.5.4

Comments

@kulaginm
Copy link
Member

In cases where:
1.the original database is no longer on timeline 1
2.the target database does not lag behind the original one in timeline,
sanity checks for incremental catchup give a false alarm and prevent databases from being synchronized with an error
ERROR: Destination is not in source timeline history

Thanks to Vadim Ponomarev ("Скала-Р") for pointing out this error.
@kulaginm kulaginm added this to the 2.5.4 milestone Dec 27, 2021
@kulaginm kulaginm self-assigned this Dec 27, 2021
@kulaginm kulaginm linked a pull request Dec 27, 2021 that will close this issue
[PGPRO-6037] fix catchup timeline history checking #462
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kulaginm kulaginm

Labels
None yet
Projects
None yet
Milestone
2.5.4
Development

Successfully merging a pull request may close this issue.

[PGPRO-6037] fix catchup timeline history checking postgrespro/pg_probackup
1 participant
@kulaginm