PgQue: Zero-Bloat Postgres Queue

Article

• PgQue uses TRUNCATE semantics instead of SKIP LOCKED to avoid Postgres VACUUM pressure
• Workers maintain cursors over append-only log; failed workers cause table growth, not data loss
• Positioned as Kafka-like log rather than traditional job queue

Discussion

• Commenters note it lacks true queue semantics (acks, shared worker pool); closer to Kafka/SNS
• SKIP LOCKED + polling cited as causing severe DB perf issues at scale in real deployments
• Postgres-native approach appealing for teams wanting to avoid Kafka/RabbitMQ operational overhead

Discuss on HN