omni_worker

Overview

Version

Build

You can build the RPM / DEB packages for omnigres using pig build:

pig build pkg omnigres         # build RPM / DEB packages

Install

You can install omnigres directly. First, make sure the PGDG and PIGSTY repositories are added and enabled:

pig repo add pgsql -u          # Add repo and update cache

Install the extension using pig or apt/yum/dnf:

• Install
• pig
• dnf
• apt

pig install omnigres;          # Install for current active PG version

pig ext install -y omnigres -v 18  # PG 18
pig ext install -y omnigres -v 17  # PG 17
pig ext install -y omnigres -v 16  # PG 16
pig ext install -y omnigres -v 15  # PG 15
pig ext install -y omnigres -v 14  # PG 14

dnf install -y omnigres_18       # PG 18
dnf install -y omnigres_17       # PG 17
dnf install -y omnigres_16       # PG 16
dnf install -y omnigres_15       # PG 15
dnf install -y omnigres_14       # PG 14

apt install -y postgresql-18-omnigres   # PG 18
apt install -y postgresql-17-omnigres   # PG 17
apt install -y postgresql-16-omnigres   # PG 16
apt install -y postgresql-15-omnigres   # PG 15
apt install -y postgresql-14-omnigres   # PG 14

Create Extension:

CREATE EXTENSION omni_worker;

Usage

omni_worker: Generalized worker pool

The omni_worker extension provides a generalized PostgreSQL worker pool that executes arbitrary workloads within individual backend contexts.

SQL Handler

The built-in SQL handler schedules SQL statement execution in background workers.

Fire-and-forget:

SELECT omni_worker.sql('INSERT INTO logs VALUES (now(), $1)');

Returns null immediately upon scheduling.

With timeout:

SELECT omni_worker.sql('VACUUM ANALYZE my_table', wait_ms => 1000);

Returns:

• true – Execution completed successfully
• false – Execution completed with failure
• null – Execution did not complete within the timeout

The SQL handler is enabled by default but can be disabled by removing its entry from the handlers table.