Full row data fetch while indexing in Elastic DB on trigger notification #459
Unanswered
SaiSingamsetty
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi @toluaina & Team,
I see that triggers are created by PG Sync which enables live updates between PosgtreSql & Elastic Index.
Also understood that for initial sync / pgsync broken or any comm gap, Pg sync utilises replication slots info to fetch & update in elastic db.
In triggers, I see only small info is being passed to PG_NOTIFY() and not the complete info.
I have observed this when I have enabled DEBUG logs. It logs the payload at on_notify() & poll_redis() which shows only minimal info.
How does PG Sync fetch the complete payload before inserting to Elastic DB ? Is there any other process parallely working ?
Or let me know if I have misunderstood something.
I am seeing an issue where it is not syncing in elastic db.
I see the payload reaching on_notify() & poll_redis() but missing elastic db logs. Since there are not much logs unable to find exact point which is breaking it.
Beta Was this translation helpful? Give feedback.
All reactions