pg_circuit

pg_circuit : Runtime observation, warnings and blocking for dangerous SQL statements

Overview

Packages

Source

pig build pkg pg_circuit;		# build rpm/deb

Install

Make sure PGDG and PIGSTY repo available:

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

Install this extension with pig:

pig install pg_circuit;		# install via package name, for the active PG version

pig install pg_circuit -v 18;   # install for PG 18
pig install pg_circuit -v 17;   # install for PG 17
pig install pg_circuit -v 16;   # install for PG 16

Config this extension to shared_preload_libraries:

shared_preload_libraries = 'pg_circuit';

Create this extension with:

CREATE EXTENSION pg_circuit;

Usage

Sources:

• README v0.1.0

pg_circuit inspects potentially dangerous DML and DDL on PostgreSQL 16–18. The Community edition can observe, warn or block statements. Add it to shared_preload_libraries, restart PostgreSQL, then create the extension as a superuser.

Basic protection

shared_preload_libraries = 'pg_circuit'

CREATE EXTENSION pg_circuit;
CREATE TABLE circuit_demo (id integer);
INSERT INTO circuit_demo VALUES (1);
SET pg_circuit.mode = 'enforce';
DELETE FROM circuit_demo; -- blocked
DELETE FROM circuit_demo WHERE id = 1;
SELECT * FROM pg_circuit_status();

Configuration and diagnostics

pg_circuit.mode defaults to warn; observe collects risk without warnings, and enforce blocks scores at or above the configured threshold. pg_circuit_runtime_state() reports pressure signals and pg_circuit_events() exposes recent events.

Community always reports effective runtime mode NORMAL. Pressure readings do not automatically escalate enforcement. This is a policy aid; application transactions, authorization and backups still determine data protection. Review rules and thresholds on representative queries before enabling enforcement.