# NikolayS/PgQue

PgQue – Zero-bloat Postgres queue built on top of on battle-proven Skype's PgQ. One SQL file to install, pg_cron to tick https://pgque.dev

Repository: https://github.com/NikolayS/PgQue
Canonical: https://ross.abutalabs.com/products/pgque
Language: PLpgSQL
License: Apache-2.0
License Family: permissive
Topics: job-queue, pg-tle, postgres, postgres-extension, postgresql, queue, tle, trusted-language-extensions
Last push: 2026-08-25T19:48:21+00:00

## Health v2 (maintenance only)
Score: 65/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 99, release rhythm 53, longevity 10
- inputs: {"age_days": 143, "days_push": 8, "days_rel": 100, "gap_med": null, "n_releases_24m": 1}
- flags: young
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1804, forks 38 (observed 2026-08-28T04:05:38.884272+00:00)

## What it is
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
- artifact type: library
- maturity: active
- function: message-queue, database, scheduling, streaming
- domain: databases, backend, developer-tools, microservices
- platform: self-hosted, cloud
- tags: postgres, plpgsql, pgq, job-queue, event-stream, pg-cron, no-sidecar, managed-postgres-compatible, postgresql, docker

## Member repositories
- NikolayS/PgQue (main) score 65

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:05:38.884272+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T03:21:48.188268+00:00, confidence not recorded.
  - readme: https://github.com/NikolayS/PgQue (fetched 2026-08-28T04:05:38.884272+00:00, sha e45ecdc39c46)
- Data as of 2026-08-30T08:39:29.467469+00:00.