Skip to content

catchup incorrectly checks the timeline history in some cases #463

Closed
@kulaginm

Description

@kulaginm

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.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

    pFad - Phonifier reborn

    Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

    Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


    Alternative Proxies:

    Alternative Proxy

    pFad Proxy

    pFad v3 Proxy

    pFad v4 Proxy