omni_var

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_var;

Usage

omni_var: Scoped variables

The omni_var extension provides typed variables with transaction, session, and statement scopes.

Set Variables

SELECT omni_var.set('my_var', true);              -- transaction scope
SELECT omni_var.set_session('my_var', true);       -- session scope
SELECT omni_var.set_statement('my_var', true);     -- statement scope

For explicit typing:

SELECT omni_var.set('text_var', 'value'::text);

Get Variables

SELECT omni_var.get('my_var', false);              -- transaction scope, default=false
SELECT omni_var.get_session('my_var', false);       -- session scope
SELECT omni_var.get_statement('my_var', false);     -- statement scope

The default value serves dual purposes: returned when the variable is not found, and its type specifies the expected return type.

Behavior

• If a variable is explicitly set to null, get returns null (not the default)
• Mismatched type specifications raise errors: ERROR: type mismatch DETAIL: expected integer, got boolean
• Transaction-scoped variables are bound by the enclosing transaction lifetime
• Session variables persist throughout the session duration