pgdisablelogerror

pgdisablelogerror : Disable selected SQLSTATE error codes from PostgreSQL server logging.

Overview

Packages

Source

pig build pkg pgdisablelogerror;		# build rpm/deb

Install

Make sure PGDG repo available:

pig repo add pgdg -u    # add pgdg repo and update cache

Install this extension with pig:

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

pig install pgdisablelogerror -v 18;   # install for PG 18
pig install pgdisablelogerror -v 17;   # install for PG 17
pig install pgdisablelogerror -v 16;   # install for PG 16
pig install pgdisablelogerror -v 15;   # install for PG 15
pig install pgdisablelogerror -v 14;   # install for PG 14

Config this extension to shared_preload_libraries:

shared_preload_libraries = '$libdir/pgdisablelogerror';

Create this extension with:

CREATE EXTENSION pgdisablelogerror;

Usage

Sources: README, v1.0 release, control file

pgdisablelogerror suppresses PostgreSQL server log entries for configured SQLSTATE error codes. It is useful when expected application errors, such as duplicate-key violations, are too noisy in the server log.

Enable The Hook

Load the module and restart PostgreSQL:

shared_preload_libraries = 'pgdisablelogerror'

Create the extension once in the postgres database:

CREATE EXTENSION pgdisablelogerror;

Configure SQLSTATE Codes

Set pgdisablelogerror.sqlerrcode to a comma-separated list of SQLSTATE codes:

pgdisablelogerror.sqlerrcode = '23505,23503'

An empty or NULL value disables suppression:

pgdisablelogerror.sqlerrcode = ''

To identify SQLSTATE values in normal PostgreSQL logs, add %e to log_line_prefix.

Caveats

• Version 1.0 supports PostgreSQL 14-18.
• This extension affects logging, not error behavior. Clients still receive the original error.
• Use narrow SQLSTATE lists. Suppressing broad error classes can hide real operational problems.