←back to thread

Postgres LISTEN/NOTIFY does not scale

(www.recall.ai)
570 points davidgu | 1 comments | 07 Jul 25 14:05 UTC | HN request time: 0.213s | source
Show context
shivasaxena ◴[10 Jul 25 21:17 UTC] No.44525717[source]▶
Out of curiosity: Would appreciate if others can share what other things like AccessExclusiveLock should postgres users beware of?

What I already know

- Unique indexes slow inserts since db has to acquire a full table lock

- Case statements in Where break query planner/optimizer and require full table scans

- Read only postgres functions should be marked as `STABLE PARALLEL SAFE`

replies(3): >>44525810 #>>44528659 #>>44529294 #
1. franckpachot ◴[10 Jul 25 21:26 UTC] No.44525810[source]▶
Can you provide more details? Inserting with unique indexes do not lock the table. Case statements are ok in where clause, use expression indexes to index it