Created
September 4, 2020 16:37
-
-
Save kissgyorgy/beccba1291de962702ea9c237a900c79 to your computer and use it in GitHub Desktop.
How to use PostgreSQL's LISTEN/NOTIFY as a simple message queue with psycopg2 and asyncio
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
import asyncio | |
import psycopg2 | |
# dbname should be the same for the notifying process | |
conn = psycopg2.connect(host="localhost", dbname="example", user="example", password="example") | |
conn.set_isolation_level(psycopg2.extensions.ISOLATION_LEVEL_AUTOCOMMIT) | |
cursor = conn.cursor() | |
cursor.execute(f"LISTEN match_updates;") | |
def handle_notify(): | |
conn.poll() | |
for notify in conn.notifies: | |
print(notify.payload) | |
conn.notifies.clear() | |
# It works with uvloop too: | |
# import uvloop | |
# loop = uvloop.new_event_loop() | |
# asyncio.set_event_loop(loop) | |
loop = asyncio.get_event_loop() | |
loop.add_reader(conn, handle_notify) | |
loop.run_forever() |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
import time | |
import psycopg2 | |
# dbname should be the same for the listening process | |
conn = psycopg2.connect(host="localhost", dbname="example", user="example", password="example") | |
cursor = conn.cursor() | |
conn.set_isolation_level(psycopg2.extensions.ISOLATION_LEVEL_AUTOCOMMIT) | |
while True: | |
val = time.time() | |
cursor.execute(f"NOTIFY match_updates, '{val}';") | |
time.sleep(1) |
Isn't there an SQL injection in the NOTIFY part?
Isn't there an SQL injection in the NOTIFY part?
- If you look at the definition of SQL injection at Wikipedia, in the second sentence it says "... when user input is either incorrectly filtered...". There is no user input in the snippet.
- This is an example of how to wire it up, people shouldn't copy-paste code from the internet verbatim.
@d33tah You can call the pg_notify function instead of the NOTIFY directive. You should be able to do parameter substitution with psycopg2 then.
Thank you so much for the detailed reply!
It would be quite useful @kissgyorgy if you have time to make a similar gist for psycopg
version 3
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I don't understand exactly what you are trying to do, but maybe a TRIGGER would be better for your use-case? Triggers can be used for partitioned tables too:
https://www.postgresql.org/docs/current/sql-createtrigger.html