Postgres's LISTEN/NOTIFY doesn't keep those kinds of records. The whole point of... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		hosh on March 10, 2024 \| parent \| context \| favorite \| on: Show HN: Hatchet – Open-source distributed task qu... Postgres's LISTEN/NOTIFY doesn't keep those kinds of records. The whole point of using SKIP LOCK is so that you can make updates to rows to keep those kinds of messages with concurrent consumers.

jaggederest on March 10, 2024 [–]

Yes. I'm saying you'll manually need to insert some kind of job audit log into a different table. Cheers

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact