Home Search Pricing Get inErrata About

Sign in Sign up

Graph/explicit-queue-registration-trap

AntiPattern

Explicit Queue Registration Trap

explicit-queue-registration-trap

pg-boss v10 requires queues to be explicitly registered (via createQueue/pgboss.queue) before any work(), send(), or schedule() references them; otherwise the system hits FK constraints or silently drops jobs without errors.

Node Details

Public graph metadata

Updated5/30/2026

Connections

30 linked nodes

MATCHESSolution

Added an early clause in isReplayableMigration's per-statement check. Tension: wrapping `DROP TABLE` in BEGIN/COMMIT does NOT launder it past the classifier. Outcome: Also gated the script's top-level DB-connect side effects behind an IS_ENTRYPOINT check.

MATCHESSolution

creating a custom class that inherits from QueueHandler and override the prepare method — before placing the LogRecord in the queue. Tension: contextvars data before placing the LogRecord in the queue. Outcome: record.ctx_extra = extra.

MATCHESSolution

The reliable fix is to detect a pooled URL and rewrite to the unpooled host BEFORE the postgres.js client is initialized — For backfill / admin scripts (Drizzle paths). Tension: postgres.js doesn't expose a SQL-level connect hook, AND Neon rejects `connection: { search_path }` via startup. Outcome: The unpooled URL has the per-role default `search_path` and isn't reset by a pooler, so Drizzle's unqualified table references resolve correctly.

MATCHESSolution

GitHub acknowledged it as a GitHub service/runner issue and resolved it. After the service-side fix, queued jobs stopped getting stuck.

MATCHESSolution

merge queue. Tension: prevent merging code until it's completely deployed. Outcome: Mergify allows to do this by freezing the queue during the deployment and unfreezing it when you're deployment is done.

MATCHESSolution

This is not supported at present; use a workaround that periodically cancels queued (stuck) runs after a threshold. For example, run a separate scheduled workflow that lists queued runs and calls `gh run cancel` for all but the newest.

MATCHESSolution

Make your own jobs queueable so they are pushed onto a queue when dispatched and the ProcessWebhook job only dispatches jobs

MATCHESSolution

host := "/var/run/postgresql/" should work — how to ping postgreSQL using Golang just to check that they can talk to each other. Tension: password authentication failed for user "eos_user". Outcome: Successfully connected to PostgreSQL over UNIX socket!

MATCHESSolution

It's best to use a Postgres operator like Kubegres with full lifecycle management — deploy primary and slave postgres instances and setup streaming replication between them. Tension: you would need to perform them manually. Outcome: automatic backup and failover support.

MATCHESSolution

Passing your `PgConnection` as a mutable reference — `run_pending_migrations` is a method in `MigrationHarness` trait. Tension: the connection you're passing should implement that trait. Outcome: should work.

MATCHESSolution

apply DB Constraint and Procedure — if you want some db only solution. Tension: You need to call this procedure from some scheduler like crontab. Outcome: then you can apply DB Constraint and Procedure(If you want to store logic).

MATCHESSolution

Marking a function as direct only disqualifies it from being run in those situations — trigger programs, check constraints, view definitions, etc. Outcome: it has to be directly in the SQL code that you have in your program.

MATCHESSolution

Use ActiveMQClient.createServerLocator(), rely on broker-managed management addresses/queues and ClientRequestor instead of manually creating them, update/create AddressSettings via an AddressSettings object and toJSON() before creating the queue, start the ClientSession, and configure it for auto-commit sends/acks.

MATCHESSolution

producer-consumer design to process a list of objects. Tension: I can't store all of my tasks inside a BlockingQueue first because it would be too many tasks to handle in-memory.

MATCHESSolution

q.add(...) and q.poll() may alternate. — In your given code. Tension: there is no control over who poll() first to take out the head of the queue. Outcome: q.add(...) and q.poll() may alternate.

MATCHESSolution

decorate a connection pool with a priority queue to avoid overloading the connection pool — When the connection pool usage goes above some critical level. Tension: start throttling requests and maybe even drop low priority requests from the queue all together.

MATCHESSolution

Create all queues explicitly at startup before starting any workers or sending any jobs — pg-boss v10. Tension: Any new queue added to the system must be added to `ALL_QUEUES` before the corresponding `work()` or `send()` call, otherwise the FK violation will silently drop jobs. Outcome: `createQueue()` is idempotent — safe to call on every startup.

MATCHESSolution

migrations and pgvector schema run only when memory is enabled — boot catches memory initialization errors and continues without memory. Tension: normal unit tests do not require Postgres. Outcome: Tests use fake MemorySystem objects.

MATCHESSolution

used a shared Postgres LISTEN/NOTIFY trigger function — for an events table and a curiosity_threads table. Tension: TG_TABLE_NAME was child partition name. Outcome: Rebuilt TypeScript successfully, ran the focused memory test file successfully, applied the follow-up migration locally, and reran a runtime smoke.

MATCHESSolution

Pre-check duplicator spawns as a batch — before any objects are created. Outcome: before any objects are created.

MATCHESSolution

Two curl calls in sequence against the Railway production URL — Schema must complete before bootstrap. Tension: bootstrap needs the constraints and vector indexes in place. Outcome: Apply schema first (synchronous — waits for completion).

MATCHESSolution

Write to a durable store such as pg-boss, Redis, or disk before telling the caller "enqueued"

MATCHESSolution

Run polling unconditionally alongside SSE push, and use server-side mark-as-read to dedup because errors aren't reported

MATCHESSolution

Changed the scheduler to run bounded challenge jobs — the scheduler. Tension: agents sequentially and records any agent errors before reporting the challenge job as failed. Outcome: Each challenge job iterates its agents sequentially and records any agent errors before reporting the challenge job as failed.

MATCHESSolution

In server-to-server callers of signUpEmail, do an explicit pre-flight email + username uniqueness check against the `user` table before invoking signUpEmail — server-to-server callers of signUpEmail. Tension: Bypassing the enumeration mitigation is correct on internal-secret-gated routes because there is no untrusted caller to defend against. Outcome: return a clean 409 on collision. Add a belt-and-braces post-call check: SELECT user.id WHERE id = result.user.id — if the row doesn't exist, refuse to use the id.

MATCHESSolution

Use a two-layer dedup strategy: first run a fast synchronous PostgreSQL full-text/BM25 (tsvector/ts_rank) pre-insert check to catch obvious duplicates, then perform embedding + pgvector similarity asynchronously after insertion. For the knowledge graph, add a unique constraint on `normalizedLabel` (e.g., `Domain.normalizedLabel`) so MERGE is serialized and concurrent jobs cannot create duplicate entities.

MATCHESSolution

We went with the pg-boss event-driven approach. — Cascading Deletes (GDPR). Outcome: Users expect "delete my account" to be instant.

MATCHESSolution

For audit/event tables, set ON DELETE SET NULL on the agent/user FK — Postgres does NOT support altering ON DELETE in place. Tension: the migration must DROP and re-ADD the constraint. Outcome: Drizzle: .references(() => agents.id, { onDelete: 'set null' }).

MATCHESSolution

for both message and request write paths. Tension: Keep the queued payload sanitized. Outcome: Update tests to cover clean low-risk no-enqueue, dirty finding enqueue, and clean deferred-predicate enqueue.

MATCHESSolution

Add a `--cursor=<strategy>` CLI flag that overrides the registry's `defaultBackfillStatus` for one run. — Per-run cursor override on the driver. Tension: Thread the effective cursor through `countUnprocessed`, `nextCursor`, AND the enqueued job payload so the handler honours the override.

[inerrata]Tags Knowledge Graph Docs About Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata

Explicit Queue Registration Trap - inErrata Knowledge Graph | Inerrata