Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Developer Tools
Postgres Job Queue
PostgreSQL-based job queue with priority scheduling, batch claiming, and progress tracking. Use when building job queues without external dependencies. Triggers on PostgreSQL job queue, background jobs, task queue, priority queue, SKIP LOCKED.
skill openclawclawhub Free
PostgreSQL-based job queue with priority scheduling, batch claiming, and progress tracking. Use when building job queues without external dependencies. Triggers on PostgreSQL job queue, background jobs, task queue, priority queue, SKIP LOCKED.
โฌ 0 downloads โ
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- README.md, SKILL.md
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 1.0.0
Provenance
- Publisher
- wpank
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
PostgreSQL Job Queue
Production-ready job queue using PostgreSQL with priority scheduling, batch claiming, and progress tracking.
When to Use
Need job queue but want to avoid Redis/RabbitMQ dependencies Jobs need priority-based scheduling Long-running jobs need progress visibility Jobs should survive service restarts
Schema Design
CREATE TABLE jobs ( id UUID PRIMARY KEY DEFAULT gen_random_uuid(), job_type VARCHAR(50) NOT NULL, priority INT NOT NULL DEFAULT 100, status VARCHAR(20) NOT NULL DEFAULT 'pending', data JSONB NOT NULL DEFAULT '{}', -- Progress tracking progress INT DEFAULT 0, current_stage VARCHAR(100), events_count INT DEFAULT 0, -- Worker tracking worker_id VARCHAR(100), claimed_at TIMESTAMPTZ, -- Timing created_at TIMESTAMPTZ DEFAULT NOW(), started_at TIMESTAMPTZ, completed_at TIMESTAMPTZ, -- Retry handling attempts INT DEFAULT 0, max_attempts INT DEFAULT 3, last_error TEXT, CONSTRAINT valid_status CHECK ( status IN ('pending', 'claimed', 'running', 'completed', 'failed', 'cancelled') ) ); -- Critical: Partial index for fast claiming CREATE INDEX idx_jobs_claimable ON jobs (priority DESC, created_at ASC) WHERE status = 'pending'; CREATE INDEX idx_jobs_worker ON jobs (worker_id) WHERE status IN ('claimed', 'running');
Batch Claiming with SKIP LOCKED
CREATE OR REPLACE FUNCTION claim_job_batch( p_worker_id VARCHAR(100), p_job_types VARCHAR(50)[], p_batch_size INT DEFAULT 10 ) RETURNS SETOF jobs AS $$ BEGIN RETURN QUERY WITH claimable AS ( SELECT id FROM jobs WHERE status = 'pending' AND job_type = ANY(p_job_types) AND attempts < max_attempts ORDER BY priority DESC, created_at ASC LIMIT p_batch_size FOR UPDATE SKIP LOCKED -- Critical: skip locked rows ), claimed AS ( UPDATE jobs SET status = 'claimed', worker_id = p_worker_id, claimed_at = NOW(), attempts = attempts + 1 WHERE id IN (SELECT id FROM claimable) RETURNING * ) SELECT * FROM claimed; END; $$ LANGUAGE plpgsql;
Go Implementation
const ( PriorityExplicit = 150 // User-requested PriorityDiscovered = 100 // System-discovered PriorityBackfill = 30 // Background backfills ) type JobQueue struct { db *pgx.Pool workerID string } func (q *JobQueue) Claim(ctx context.Context, types []string, batchSize int) ([]Job, error) { rows, err := q.db.Query(ctx, "SELECT * FROM claim_job_batch($1, $2, $3)", q.workerID, types, batchSize, ) if err != nil { return nil, err } defer rows.Close() var jobs []Job for rows.Next() { var job Job if err := rows.Scan(&job); err != nil { return nil, err } jobs = append(jobs, job) } return jobs, nil } func (q *JobQueue) Complete(ctx context.Context, jobID uuid.UUID) error { _, err := q.db.Exec(ctx, ` UPDATE jobs SET status = 'completed', progress = 100, completed_at = NOW() WHERE id = $1`, jobID, ) return err } func (q *JobQueue) Fail(ctx context.Context, jobID uuid.UUID, errMsg string) error { _, err := q.db.Exec(ctx, ` UPDATE jobs SET status = CASE WHEN attempts >= max_attempts THEN 'failed' ELSE 'pending' END, last_error = $2, worker_id = NULL, claimed_at = NULL WHERE id = $1`, jobID, errMsg, ) return err }
Stale Job Recovery
func (q *JobQueue) RecoverStaleJobs(ctx context.Context, timeout time.Duration) (int, error) { result, err := q.db.Exec(ctx, ` UPDATE jobs SET status = 'pending', worker_id = NULL, claimed_at = NULL WHERE status IN ('claimed', 'running') AND claimed_at < NOW() - $1::interval AND attempts < max_attempts`, timeout.String(), ) if err != nil { return 0, err } return int(result.RowsAffected()), nil }
Decision Tree
ScenarioApproachNeed guaranteed deliveryPostgreSQL queueNeed sub-ms latencyUse Redis instead< 1000 jobs/secPostgreSQL is fine> 10000 jobs/secAdd Redis layerNeed strict orderingSingle worker per type
Related Skills
Related: service-layer-architecture โ Service patterns for job handlers Related: realtime/dual-stream-architecture โ Event publishing from jobs
NEVER Do
NEVER use SELECT then UPDATE โ Race condition. Use SKIP LOCKED. NEVER claim without SKIP LOCKED โ Workers will deadlock. NEVER store large payloads โ Store references only. NEVER forget partial index โ Claiming is slow without it.
Category context
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
2 Docs
- SKILL.md
- README.md