WIP sql: implement LISTEN/NOTIFY/UNLISTEN#48308
WIP sql: implement LISTEN/NOTIFY/UNLISTEN#48308jordanlewis wants to merge 1 commit intocockroachdb:masterfrom
Conversation
|
This change is |
170eb6a to
a68e5f5
Compare
|
Wonderful |
58786ea to
4e985c8
Compare
|
@jordanlewis What's the current state of this PR? I'd like to use this feature. |
|
@enumag Unfortunately, it's completely out of date and unfinished. I'd like to resurrect it at some point, but I don't have a timeline to offer you for that. |
|
I see. Thanks for replying. 🙂 |
fdf5788 to
7282965
Compare
|
Just wanted to check in and mention that this would be very useful for async job handling in Rails, where several of the popular adapters use LISTEN/NOTIFY (for example https://github.com/bensheldon/good_job) |
7282965 to
c292395
Compare
c292395 to
4849572
Compare
Closes cockroachdb#41522. This commit enables LISTEN/NOTIFY. One problem is that the 32 bit session ID is back to bite us from cockroachdb#34520. We don't have a 32 bit identifier that's unique across all sessions of the cluster. Currently, we report the NodeID for the PID of the notifying process instead. Release note (sql change): implement the LISTEN/NOTIFY Postgres protocol; LISTEN, NOTIFY, UNLISTEN, and pg_notify.
4849572 to
e19cebc
Compare
|
Quite a good feature to implement. Why its not being shown some love ? Are you guys considering this somewhere in near future or its off the roadmap forever ? |
|
Is this still planned/being worked on? Last commit is from 2 years ago |
Closes #41522.
One problem is that the 32 bit session ID is back to bite us
from #34520. We don't have a 32 bit identifier that's unique across all
sessions of the cluster. Currently, we report 0 for the PID of the
notifying process, which probably isn't going to fly.
Release note (sql change): implement the LISTEN/NOTIFY Postgres
protocol and statement suite