docs(blueprints): 45-min podcast talking points

[NikolayS]

Summary

Adds blueprints/podcast-talking-points.md — internal prep for a 45-minute podcast about PgQue. Lives under blueprints/ (brainstorms / non-user-facing) per CLAUDE.md, not under docs/.

The doc structures the conversation around four load-bearing ideas:

1. Bloat is a design problem, not a tuning problem. SKIP LOCKED queues UPDATE + DELETE on the hot path; dead tuples can't be reclaimed past a held xmin horizon. Receipts: Brandur/Heroku 2015, PlanetScale 2026, River docs: slim README and add docs/ tree for v0.1 #59.
2. PgQ's actual answer. Snapshot-based batching (the queue is a virtual cursor over a shared log, not a worklist of mutated rows) + TRUNCATE-based table rotation (zero dead tuples by construction).
3. The "anti-extension" repackage. Why PgQ never spread (C extension + pgqd daemon don't run on managed Postgres) and what PgQue does about it (single-file \i pgque.sql install, pg_cron sub-second ticking trick, modern send/receive/ack/nack API).
4. Honest trade-offs. Three latencies framing; e2e ≈ tick period and doesn't grow with load; not for sub-3ms dispatch; not a job-queue framework.

Also includes:

• 45-minute time-block arc (cold open → bloat story → architecture → repackage → trade-offs → roadmap → close).
• Q&A bank with crisp answers to the obvious host questions ("isn't this just another in-database queue?", "why not Kafka?", "how does this compare to PGMQ?", etc.).
• 3-minute demo flow.
• Stats sheet to keep on hand.
• "Things to NOT say" list (don't claim Postgres-native Kafka, don't trash SKIP LOCKED categorically).

Test plan

• Read end-to-end against the README and verify every claim ties to a section in README.md, docs/three-latencies.md, docs/tick-frequency.md, or docs/pgq-history.md.
• Sanity-check the demo flow against docs/tutorial.md so the on-air commands match what new users actually run.
• Confirm tone matches CLAUDE.md docs guidance (no PR/issue numbers in user-facing docs — this one lives under blueprints/ so internal references are allowed there, but still kept minimal).

---

Generated by Claude Code