catchup incorrectly checks the timeline history in some cases · Issue #463 · postgrespro/pg_probackup (original) (raw)

Skip to content

Navigation Menu

• • GitHub Copilot Write better code with AI
  • GitHub Advanced Security Find and fix vulnerabilities
  • Actions Automate any workflow
  • Codespaces Instant dev environments
  • Issues Plan and track work
  • Code Review Manage code changes
  • Discussions Collaborate outside of code
  • Code Search Find more, search less
• Explore
  • Learning Pathways
  • Events & Webinars
  • Ebooks & Whitepapers
  • Customer Stories
  • Partners
  • Executive Insights
• • GitHub Sponsors Fund open source developers
  • The ReadME Project GitHub community articles
• • Enterprise platform AI-powered developer platform
• Pricing

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Sign up

Appearance settings

Description

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.