Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wgPhM-006Ako-01 for pgsql-announce@arkaria.postgresql.org; Sun, 05 Jul 2026 16:28:04 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wgPhK-00CpGc-2T for pgsql-announce@arkaria.postgresql.org; Sun, 05 Jul 2026 16:28:02 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wgPcc-00CTtc-2b for pgsql-announce@lists.postgresql.org; Sun, 05 Jul 2026 16:23:10 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wgPcZ-00000001tQy-1qQS for pgsql-announce@lists.postgresql.org; Sun, 05 Jul 2026 16:23:10 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Message-ID:Date:Reply-To:From:To:Subject: MIME-Version:Content-Type:Sender:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:In-Reply-To:References; bh=TGY0uPIicF+uJj4QrOxmWQlct/F8JrzIB5aMOBYNFwk=; b=DZe02TSQQivCzZXQzeeVsEdVXL Yjxv6bUYw+xoulqawsBnDegkRkItkMkCj2DwjP3wK2fO2xbpHt1edCrEwiPjQobA+CtLTazE7657y VvMxP0ULWFn4fDEhZ6wzwpZBF5spG8f6yA6LuJK/Ivltp4+hLJG0Hpe6iaBukbEZZUt26hxmm6mm4 TRom5fu2H/nnwJlc7BRYq0+aC7DV97/HJEeZjh3FBrcfIl9oPbuKTQTXUWHo1VYUuFXoKltJ28PJF Qyn71Y4Jv7saiwlv7yf7j674GUB7MfoK1HCXtWIcfAObouVzmY0hvEhJ7ehYNwApnHzm3rzMm+nq+ HWQE179A==; Received: from wrigleys.postgresql.org ([2a02:16a8:dc51::60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wgPcX-00B91C-2R for pgsql-announce@lists.postgresql.org; Sun, 05 Jul 2026 16:23:06 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wgPcV-00DK4u-2e for pgsql-announce@lists.postgresql.org; Sun, 05 Jul 2026 16:23:03 +0000 Content-Type: multipart/alternative; boundary="===============5536925158298753122==" MIME-Version: 1.0 Subject: pg_dbms_errlog v2.4 released To: PostgreSQL Announce From: HexaCluster via PostgreSQL Announce Reply-To: gilles@hexacluster.ai Date: Sun, 05 Jul 2026 16:22:32 +0000 Message-ID: <178326855296.108990.4929541544083665376@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-pglister-tags: related X-pglister-tagsig: ce618f9dcad84e19627c72494c2127409d0281d78f7c99a820d7abeae67fb89d List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --===============5536925158298753122== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Bangkok, Thailand - June 23, 2026 ## PostgreSQL DBMS_ERRLOG compatibility extension The pg_dbms_errlog extension provides the infrastructure that enables you t= o create an error logging table so that DML operations can continue after e= ncountering errors rather than abort and roll back. It requires the use of = the pg_statement_rollback extension or to fully manage the SAVEPOINT in the= DML script. Logging in the corresponding error table is done using dynamic= shared memory for error queuing and a background worker to write the error= s queued into the corresponding error log tables. Note that configuration s= etting max_worker_processes must be high enough to support the extension, a= s it will launch up to pg_dbms_errlog.max_workers dynamic background worker= s, plus an additional fixed background worker. pg_dbms_errlog v2.3 and v2.4 has been released, they are maintenance releas= es to add compatibility with PostgreSQL 18 and 19 and fix two major bugs. Complete list of changes and acknowledgments are available here [v2.3](http= s://github.com/HexaCluster/pg_dbms_errlog/releases/tag/v2.3) - [v2.4](https= ://github.com/HexaCluster/pg_dbms_errlog/releases/tag/v2.4) Error logging can be done synchronously by registering the error at query l= evel or when the transaction ends using GUC pg_dbms_errlog.synchronous. Log= ging at transaction is the default and must be preferred to query, it is th= e mode that can guarantee that only errors on a committed transaction will = be logged. When synchronous logging is disabled off error logging is done w= hen the bg_worker wakes up or when function dbms_errlog.publish_queue() is = called or that the synchronous level is changed. ## Links & Credits pg_dbms_errlog is an open project under the PostgreSQL license maintained b= y [HexaCluster](https://github.com/HexaCluster/credcheck/) and created by G= illes Darold as part of the improvement of Ora2Pg. Any contribution to buil= d a better tool is welcome. You can send your ideas, features requests or p= atches using the GitHub tools. **Links :** * Download: [https://github.com/HexaCluster/pg_dbms_errlog/releases/](http= s://github.com/HexaCluster/pg_dbms_errlog/releases/) * Support: use GitHub report tool at [https://github.com/HexaCluster/pg_dbm= s_errlog/issues](https://github.com/HexaCluster/pg_dbms_errlog/issues) ## About pg_dbms_errlog Documentation at [https://github.com/HexaCluster/pg_dbms_errlog#readme](htt= ps://github.com/HexaCluster/pg_dbms_errlog#readme) --===============5536925158298753122== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable pg_dbms_errlog v2.4 released
 

pg_dbms_errlog v2.4 released

Bangkok, Thailand - June 23, 2026

PostgreSQL DBMS_ERRLOG compatib= ility extension

The pg_dbms_errlog extension provides the i= nfrastructure that enables you to create an error logging table so that DML= operations can continue after encountering errors rather than abort and ro= ll back. It requires the use of the pg_statement_rollback extension or to f= ully manage the SAVEPOINT in the DML script. Logging in the corresponding e= rror table is done using dynamic shared memory for error queuing and a back= ground worker to write the errors queued into the corresponding error log t= ables. Note that configuration setting max_worker_processes must be high en= ough to support the extension, as it will launch up to pg_dbms_errlog.max_w= orkers dynamic background workers, plus an additional fixed background work= er.

pg_dbms_errlog v2.3 and v2.4 has been relea= sed, they are maintenance releases to add compatibility with PostgreSQL 18 = and 19 and fix two major bugs.

Complete list of changes and acknowledgment= s are available here = v2.3 - v2.4

Error logging can be done synchronously by = registering the error at query level or when the transaction ends using GUC= pg_dbms_errlog.synchronous. Logging at transaction is the default and must= be preferred to query, it is the mode that can guarantee that only errors = on a committed transaction will be logged. When synchronous logging is disa= bled off error logging is done when the bg_worker wakes up or when function= dbms_errlog.publish_queue() is called or that the synchronous level is cha= nged.

Links & Credits

pg_dbms_errlog is an open project under the= PostgreSQL license maintained by HexaClust= er and created by Gilles Darold as part of the improvement of Ora2Pg. A= ny contribution to build a better tool is welcome. You can send your ideas,= features requests or patches using the GitHub tools.

Links :

About pg_dbms_errlog

Documentation at https://github.com/HexaCluster/pg_dbms_errlog#readme

This email was sent to you from HexaCluster. It was delivered on their beha= lf by the PostgreSQL project. Any questions about the content of the message shou= ld be sent to HexaCluster.

You were sent this email as a subscriber of the pgsql-announce mai= linglist, for the content tag Related Open Source. To unsubscribe from further emails, or change which emails you want to receive, please click th= e personal unsubscribe link that you can find in the headers of this email, or visit https://lists.postgresql.org/unsubscribe/.
 
--===============5536925158298753122==--