Hacker News: jeeybee

Show HN: PgQueuer v1.0 – Python job queue using only PostgreSQ

jeeybee — Mon, 11 May 2026 20:22:13 +0000

PgQueuer is a Python job queue that uses PostgreSQL for everything — queue storage, locking, notifications. No Redis, no RabbitMQ, no separate broker to operate. If your app already has Postgres, you already have the broker.

After ~2 years and 26 minor releases, 1.0 ships today as the first stable release. Strict semver from here on.

Thanks to everyone who contributed and left feedback!

Comments URL: https://news.ycombinator.com/item?id=48100177

Points: 2

# Comments: 0

New comment by jeeybee in "Show HN: Rekal – Long-term memory for LLMs in a single SQLite file"

jeeybee — Tue, 14 Apr 2026 06:13:17 +0000

Added a mcp command for it, but i might add it as a comfig as well?

https://github.com/janbjorge/rekal/pull/14/changes

New comment by jeeybee in "Show HN: Rekal – Long-term memory for LLMs in a single SQLite file"

jeeybee — Mon, 13 Apr 2026 21:10:34 +0000

Thanks, i will look into making them configurable.

New comment by jeeybee in "Show HN: Rekal – Long-term memory for LLMs in a single SQLite file"

jeeybee — Mon, 13 Apr 2026 21:10:23 +0000

The 0.4/0.4/0.2 weights are just based of hand wavy trail an error, will look into other options. I could make them configurable?

New comment by jeeybee in "Show HN: Rekal – Long-term memory for LLMs in a single SQLite file"

jeeybee — Mon, 13 Apr 2026 06:16:25 +0000

Thanks! You're right, that's just a relic of my dev environment. Will broaden the version requirement.

Show HN: Rekal – Long-term memory for LLMs in a single SQLite file

jeeybee — Sun, 12 Apr 2026 21:25:53 +0000

I got tired of repeating myself to my LLM every session. rekal is an MCP server that stores memories in SQLite and retrieves them with hybrid search (BM25 + vectors + recency decay). One file, local embeddings, no API keys.

Comments URL: https://news.ycombinator.com/item?id=47744683

Points: 9

# Comments: 10

New comment by jeeybee in "Keeping a Postgres Queue Healthy"

jeeybee — Sat, 11 Apr 2026 19:07:46 +0000

Did you test with fillfactor < 100 on the queue table? With HOT updates, status changes can reuse dead space without creating new index entries, which seems like it could significantly delay the onset of the death spiral?

New comment by jeeybee in "Show HN: Pglens – 27 read-only PostgreSQL tools for AI agents via MCP"

jeeybee — Mon, 30 Mar 2026 18:37:27 +0000

No config step, the tools discover everything from pg_catalog at call time. list_schemas → list_tables → describe_table is the typical agent workflow, and there's a query_guide prompt baked in that suggests that progression.

On query guardrails: every query runs in a readonly transaction and results are capped at 500 rows via a wrapping SELECT * FROM (...) sub LIMIT 500. There's also explain_query which returns the plan without executing, so agents can check before running something expensive. That said, there's no cost-based gate that blocks a bad plan automatically; that's an interesting idea worth exploring.

New comment by jeeybee in "Show HN: Pglens – 27 read-only PostgreSQL tools for AI agents via MCP"

jeeybee — Mon, 30 Mar 2026 17:00:50 +0000

Thanks! Read-only felt like the obvious constraint; agents shouldn't need write access to understand a database.

New comment by jeeybee in "Show HN: Pglens – 27 read-only PostgreSQL tools for AI agents via MCP"

jeeybee — Sun, 29 Mar 2026 16:31:22 +0000

Most Postgres MCP servers expose query and list_tables. Agents end up guessing column values, enum casing, and join paths - then retrying until something works.

pglens gives agents the context to get it right the first time: column_values shows real distinct values with counts, find_join_path does BFS over the FK graph and returns join conditions through intermediate tables, describe_table gives columns/PKs/FKs/indexes in one call. Plus production health tools like bloat_stats, blocking_locks, and sequence_health.

Everything runs in readonly transactions, identifiers escaped via Postgres's quote_ident(), no extensions required. Works on any Postgres 12+ (self-hosted, RDS, Aurora, etc.). Two dependencies: asyncpg and mcp.

https://github.com/janbjorge/pglens

pip install pglen

Show HN: Pglens – 27 read-only PostgreSQL tools for AI agents via MCP

jeeybee — Sun, 29 Mar 2026 16:30:36 +0000

Article URL: https://github.com/janbjorge/pglens

Comments URL: https://news.ycombinator.com/item?id=47564620

Points: 13

# Comments: 7

Show HN: Pglens – Postgres MCP server that lets agents look before they query

jeeybee — Mon, 23 Mar 2026 19:43:21 +0000

Article URL: https://github.com/janbjorge/pglens

Comments URL: https://news.ycombinator.com/item?id=47494195

Points: 3

# Comments: 0

Show HN: GYML – YAML syntax, JSON semantics, zero runtime dependencies

jeeybee — Sun, 08 Mar 2026 22:55:51 +0000

YAML keeps surprising people in production. The Norway Problem (`NO` parsed as `False`). Silent duplicate key overwrites. The spec has 211 grammar productions. Most of that complexity exists to support features nobody wanted in a config file.

GYML is a strict subset of YAML. Valid GYML is always valid YAML. It keeps the block indentation syntax and pairs it with JSON's type semantics: one spelling for each type, no anchors, no aliases, no tags, duplicate keys are a hard error. From-scratch parser, no runtime dependencies, fully typed Python.

https://github.com/janbjorge/gyml

Comments URL: https://news.ycombinator.com/item?id=47302509

Points: 1

# Comments: 0

Show HN: PgQueuer – A PostgreSQL job queue that works without PostgreSQL

jeeybee — Sun, 01 Mar 2026 21:38:06 +0000

PgQueuer turns PostgreSQL into a background job queue using LISTEN/NOTIFY and FOR UPDATE SKIP LOCKED. v0.26.0 adds an in-memory adapter so you can run the same code in tests and CI without a database. Internally it's now built on port protocols, so you can swap the persistence layer entirely.

EDIT; HN trims the full url to readme about in-memory https://github.com/janbjorge/pgqueuer?tab=readme-ov-file#in-...

Comments URL: https://news.ycombinator.com/item?id=47210945

Points: 2

# Comments: 0

Show HN: Jqueue: A job queue that runs on a single JSON file

jeeybee — Tue, 24 Feb 2026 23:14:45 +0000

I built a Python job queue that stores its entire state in one JSON file on S3, GCS, or your filesystem. No Redis, no RabbitMQ, no Postgres. Just object storage.

How it works

Read the JSON file, modify it in memory, write it back with compare-and-set. If two workers race, one wins. The loser retries with fresh state. No locks needed.

Inspired by; https://turbopuffer.com/blog/object-storage-queue

Comments URL: https://news.ycombinator.com/item?id=47144842

Points: 2

# Comments: 0

PGQueuer for High-Performance Job Queues

jeeybee — Fri, 20 Feb 2026 21:24:08 +0000

Article URL: https://alexdewey.github.io/AlexDeweyGiovanniniBlog/2026/02/20/PGqueuer.html

Comments URL: https://news.ycombinator.com/item?id=47094172

Points: 1

# Comments: 0

New comment by jeeybee in "Using PostgreSQL as a Dead Letter Queue for Event-Driven Systems"

jeeybee — Mon, 26 Jan 2026 11:03:48 +0000

I maintain a small Postgres-native job queue for Python called PGQueuer: https://github.com/janbjorge/pgqueuer

It uses the same core primitives people are discussing here (FOR UPDATE SKIP LOCKED for claiming work; LISTEN/NOTIFY to wake workers), plus priorities, scheduled jobs, retries, heartbeats/visibility timeouts, and SQL-friendly observability. If you’re already on Postgres and want a pragmatic “just use Postgres” queue, it might be a useful reference / drop-in.

New comment by jeeybee in "Kafka is Fast – I'll use Postgres"

jeeybee — Wed, 29 Oct 2025 21:58:43 +0000

If you like the “use Postgres until it breaks” approach, there’s a middle ground between hand-rolling and running Kafka/Redis/Rabbit: PGQueuer.

PGQueuer is a small Python library that turns Postgres into a durable job queue using the same primitives discussed here — `FOR UPDATE SKIP LOCKED` for safe concurrent dequeue and `LISTEN/NOTIFY` to wake workers without tight polling. It’s for background jobs (not a Kafka replacement), and it shines when your app already depends on Postgres.

Nice-to-haves without extra infra: per-entrypoint concurrency limits, retries/backoff, scheduling (cron-like), graceful shutdown, simple CLI install/migrations. If/when you truly outgrow it, you can move to Kafka with a clearer picture of your needs.

Repo: https://github.com/janbjorge/pgqueuer

Disclosure: I maintain PGQueuer.

New comment by jeeybee in "Slack has raised our charges by $195k per year"

jeeybee — Thu, 18 Sep 2025 11:27:53 +0000

I’ve always loved Slack. It’s been core to how we work, and I’ve recommended it to countless others.

But seeing how they just treated Hack Club — sudden 40x price hike, almost no notice, threatening to cut off access and delete 11 years of history — makes me wonder if we should rethink where we build our work.

I don’t want to leave Slack. But I also don’t want to wake up one day with our team’s history held hostage.

New comment by jeeybee in "Ask HN: What are you working on? (July 2025)"

jeeybee — Mon, 28 Jul 2025 12:35:39 +0000

pgqueuer turns vanilla PostgreSQL into horizontally-scalable job queue with zero extra infrastructure. If you’re running Postgres and want to ditch extra queue clusters, give it a spin and let me know how it holds up.

https://github.com/janbjorge/pgqueuer