Skip to content
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.

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

Issue with Data Synchronization in pgsync #545

Open
HalfSea opened this issue Jun 17, 2024 · 1 comment
Open

Issue with Data Synchronization in pgsync #545

HalfSea opened this issue Jun 17, 2024 · 1 comment

Comments

@HalfSea
Copy link

HalfSea commented Jun 17, 2024

PGSync version: 3.1.0

Postgres version: 14.12

Elasticsearch/OpenSearch version: 8.13.4

Redis version: 6.0.16

Python version: 3.10.12

Problem Description:
I encountered an issue while using pgsync (version 3.1.0) with PostgreSQL (version 14.12) and ElasticSearch (version 8.13.4). During the operation, ElasticSearch crashed, which also caused pgsync to stop. During this downtime, some data in a table in the PostgreSQL database was physically deleted. After restarting ElasticSearch and pgsync, new and modified data in the PostgreSQL database was synchronized correctly, but the physically deleted data was not removed in ElasticSearch, leading to data inconsistencies.

Error Message (if any):



@HalfSea
Copy link
Author

HalfSea commented Jun 18, 2024

I used a simple data table with only id and name fields to reproduce the issue but did not encounter the same problem. I will investigate further to find a reliable way to reproduce the issue and provide a detailed description.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant