-
-
Notifications
You must be signed in to change notification settings - Fork 187
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
Sync issue on child tables #569
Comments
|
|
I tried manually specifying foreign keys but also automatically, the issue stays the same
Correct
Yes, also correct
Foreign key is defined in database relation, (content.document_id) -> (document.uuid)
Yes, it happens aswell |
This has now been resolved on the main branch. Can you please try it out now? |
Thanks so much for working on this issue. Sadly, in my testing, the change seemed to make no difference. Im currently trying to debug three issues with pgsync all relating to child relations:
We probably will be looking for another indexing solution for now, but will reconsider if those issues are fixed. I dont understand the pgsync code enough to help with it. |
PGSync version: 3.2.0
Postgres version: 16.4.0
Elasticsearch/OpenSearch version: 7.16.3
Redis version: 7.4.0
Python version: 3.9
Problem Description:
Possibly related to #568, maybe also #552
Problem Description:
Take this schema:
Lets prepopulate the document table with 20 documents and no content, and let pgsync index. While pgsync is down, i populate the content table with 20 rows. After pgsync starts, only one document in index "document" has content, while in index "content" i have 20 objects.
So pgsync in my opinion seems to have a more general syncing issue related to child tables.
Error Message (if any):
The text was updated successfully, but these errors were encountered: