Replies: 1 comment 2 replies
-
Hi @kasbah .. Sorry - this one got lost in the void. Both will do, but there is less ceremony around using subscribe since you don't need to add triggers that call notify for you. You can create a publication that only publishes for the limited number of tables that you'd like updates on so I think it depends on your specific case, so if you can describe that we can get closer to the optimal solution? |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Thanks for this lovely library!
I'm looking at an application where I want to subscribe to table updates and I've managed to make a proof-of-concept with
subscribe
. I am not doing full "logical replication" however, which is whatsubscribe
, or at leastwal_level = logical
seems to be for. Should I be usinglisten
if I only want to subscribe to a very targeted and limited number of updates?On the
listen
section in the readme it says:Is that the case for
subscribe
too? Is that something I should worry about?Beta Was this translation helpful? Give feedback.
All reactions