Keeping a Postgres Queue Healthy

Re:Keeping a Postgres Queue Healthy by richwater on Saturday April 11, 2026 @02:30PM (#47732870)

It would be nice if this ad at least explained a little bit of the technical side of the solution.

[ Parent | on HN ]

Re:Keeping a Postgres Queue Healthy by simeonGriggs on Saturday April 11, 2026 @03:53PM (#47733465)

We’ve got a separate blog post all about how traffic control works: https://planetscale.com/blog/behind-the-scenes-how-traffic-c...

[ Parent | on HN ]

Re:Keeping a Postgres Queue Healthy by sgarland on Saturday April 11, 2026 @02:48PM (#47733016)

It sounds vaguely like InnoDB’s concurrency control solution which uses tokens [0] as a unit of maximum work a query can perform.

0: https://dev.mysql.com/doc/refman/8.4/en/innodb-performance-t...

[ Parent | on HN ]

Re:Keeping a Postgres Queue Healthy by sroussey on Saturday April 11, 2026 @07:43PM (#47734943)

tickets, not tokens, but yeah

[ Parent | on HN ]

Re:Keeping a Postgres Queue Healthy by dukepiki on Sunday April 12, 2026 @01:08AM (#47736303)

MySQL’s concurrency control is a limit on the total number of threads that can be active at once, across all queries.

Traffic Control limits concurrency and resource use according to configurable metadata like the username, remote address, or the contents of any sqlcommenter tags included in the query. So you can say things like “the batch processing role can’t run more than four queries at a time.” The finer granularity is key.

[ Parent | on HN ]