-
-
Notifications
You must be signed in to change notification settings - Fork 172
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
New documents not being created on database insert #182
Comments
I think the getting started section might be the best things we have. https://pgsync.com/getting-started. The logs suggest it is pushing to Elasticsearch. Do you see any error previously? |
@toluaina , even I am facing the same Issue. New records are not going to ES, but it is showing polling count correctly in PGSync logs. Also I noticed that if we restart PGSync all the records sync to ES correctly. But its not ideal to restart it everytime. |
Data is first held in the replication logs and sometimes this needs |
i did initial sync via In which direction should I look? Is there a way we can make sure that all the data are get indexed and flush the logs from the replica slot and reset pgsync pulling count to 0 in files? |
@AnkitKundariya |
@toluaina I have my schema with the following details: If i am trying to edit existing user, its reflecting the changes in Elasticsearch but its not reflecting new user entry in Elasticsearch. Delete is also working. |
Hello, I am running the docker version of the airbnb demo. When I insert new records into postgres, I am not seeing the elastic search document count increase. I do however see "Polling db airbnb: 2 item(s)" logged
![Screen Shot 2021-09-27 at 12 52 55 PM](https://user-images.githubusercontent.com/4350219/134960876-cf7297f4-35e2-4801-81c9-956e50d3d818.png)
.
Also, are there instructions on how to setup pgsync for an existing database somewhere? I want to continue running pgsync in docker, but have it work with a db running on bare metal on my local Mac.
Thanks
Lane
The text was updated successfully, but these errors were encountered: