PgQue is a pure SQL/PLpgSQL event queue for Postgres 14+ that delivers durable, Kafka-style streams without dead tuples or external daemons. It uses snapshot-based batching and TRUNCATE-driven table rotation for stable performance under sustained load. A pg_cron (or any scheduler) ticker drives 1–2 second end-to-end delivery.

• Uses snapshot-based batching with TRUNCATE-driven table rotation instead of per-row UPDATE/DELETE with SKIP LOCKED, avoiding dead tuples, VACUUM pressure, and bloat under sustained load.
• Pure SQL/PLpgSQL install (single file) with pg_cron ticking every second, so it runs on managed Postgres without C extensions or custom builds—unlike PgQ, PGMQ, River, Que, and pg-boss.
• Offers Kafka-style shared event logs with independent per-consumer cursors, rather than one-job-one-worker task queue semantics.
• Delivery latency is 1–2 seconds (tick interval plus polling), with microsecond function execution—fine for durability-focused use but not for sub-millisecond dispatch needs.