The normal way around this in Postgres is to use NOTIFY to merely signal that there is something new, and use a separate (perhaps transactional) work queue to c

The normal way around this in Postgres is to use NOTIFY to merely signal that there is something new, and use a separate (perhaps transactional) work queue to claim a row to process. You’re correct that relying on parameters in the actual notification will lose work.