NikolayS/PgQue

Health v2 · maintenance only

Flags: young

Adoption not part of the score

1804 stars · 38 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

PgQue is a zero-bloat job/event queue for PostgreSQL implemented in pure SQL and PL/pgSQL, rebuilt from Skype's battle-tested PgQ architecture. It installs as a single SQL file, requires no C extension or sidecar daemon, and works on any Postgres 14+ including managed providers, using pg_cron or pg_timetable to tick.

Use cases

• run a durable event stream inside Postgres without external daemons
• add a job queue to a managed Postgres provider that forbids C extensions
• replace SKIP LOCKED queue tables that bloat under sustained load
• build Kafka-like per-consumer cursor event logs in Postgres
• queue background jobs using only SQL and PL/pgSQL
• migrate legacy PgQ workloads to modern managed Postgres

When to choose

• you already run PostgreSQL and want a queue without new infrastructure
• you're on managed Postgres (RDS, Cloud SQL, Supabase) where C extensions and daemons aren't allowed
• you need a durable shared event log with independent consumer cursors rather than a task broker
• you want zero-bloat behavior under sustained load

When to avoid

• you need very low latency or high-throughput messaging beyond what Postgres can handle
• you need a full-featured task broker with routing, exchanges, or fan-out like RabbitMQ
• your stack already uses a dedicated message broker or Kafka
• you need client SDKs for languages beyond the available client libraries

Facets

library · maturity active

message-queue database scheduling streaming databases backend developer-tools microservices self-hosted cloud postgres plpgsql pgq job-queue event-stream pg-cron no-sidecar managed-postgres-compatible postgresql docker

Member repositories

For agents

markdown · JSON · MCP: product_card(name="NikolayS/PgQue")