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.94.2) (envelope-from ) id 1v3wQM-005tez-Li for pgsql-announce@arkaria.postgresql.org; Wed, 01 Oct 2025 12:59:15 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1v3wQJ-00232S-R6 for pgsql-announce@arkaria.postgresql.org; Wed, 01 Oct 2025 12:59:12 +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.94.2) (envelope-from ) id 1v3wQI-0022xd-T1 for pgsql-announce@lists.postgresql.org; Wed, 01 Oct 2025 12:59:11 +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.96) (envelope-from ) id 1v3wQF-0015Ee-36 for pgsql-announce@lists.postgresql.org; Wed, 01 Oct 2025 12:59: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=ZDv3/2/I9/QLu06rbGbVHviOm9PPPLHaDTKpV0jH4s0=; b=tnwzEu1nuJw3RhZvPmjKmXn4Pb 3n/sdVXNwkwonuy2wiS635hcZcqUH3tB258XFxENrz244iIBPIWwtfOL4aWcqtgmXXJaJPrERf+S7 8fbZ02bplGiKd1OfBUDpRH2aAPuhJjms7Qz7F40OeF7AAW3p0FQnUaN2Bklo+Ww8R2ZkmlEfkQ521 7Kt0lMB12QVRW/NBeyBChAIwaF/dcxr1DSfmwEfFjLrBTnXUspqxdxKkoeNzGYJjhwa0CmyS0A/67 6mloOPfPCAjDTfGmC4jbhHesBC1ABnfV+e1UtkjByZvmKeo1xe7YVPozZwXykKaVCxyyanloGg1Fj qW/I8/6Q==; Received: from wrigleys.postgresql.org ([217.196.149.60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1v3wQD-002Op1-7w for pgsql-announce@lists.postgresql.org; Wed, 01 Oct 2025 12:59: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 1v3wQB-004q3p-2Y for pgsql-announce@lists.postgresql.org; Wed, 01 Oct 2025 12:59:03 +0000 Content-Type: multipart/mixed; boundary="===============0430783575163792744==" MIME-Version: 1.0 Subject: pg_statement_rollback v1.5 released To: PostgreSQL Announce From: HexaCluster via PostgreSQL Announce Reply-To: gilles@hexacluster.ai Date: Wed, 01 Oct 2025 12:58:06 +0000 Message-ID: <175932348663.817.757922438321459701@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-pglister-tags: related X-pglister-tagsig: 3f4174122bc75e2533d706a213a61aa9f692f92b310802bd1565c1df878991bc List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --===============0430783575163792744== Content-Type: multipart/alternative; boundary="===============8556133435148426556==" MIME-Version: 1.0 --===============8556133435148426556== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Dar Es Salam - September 29th, 2025 ## Server side rollback at statement level for PostgreSQL pg_statement_rollback is a PostgreSQL extension to add server side transaction with rollback at statement level like in Oracle or DB2. Release v1.5 of pg_statement_rollback was released. This is a maintenance release to add support to PostgreSQL 18. See [ChangeLog](https://github.com/lzlabs/pg_statement_rollback/releases/ta= g/v1.5) for a complete list of changes. ## Links & Credits pg_statement_rollback is an open project orignaly from LzLabs and now maint= ained by Gilles Darold at [HexaCluster Corp](https://hexacluster.ai)/ Any contribution to build a better tool is welcome. You just have to send your ideas, features requests or patches using the GitHub tools. Links : * Documentation: [https://github.com/lzlabs/pg_statement_rollback/#readme](= https://github.com/lzlabs/pg_statement_rollback/#readme) * Download: [https://github.com/lzlabs/pg_statement_rollback/releases/](ht= tps://github.com/lzlabs/pg_statement_rollback/releases/) * Support: use GitHub report tool at [https://github.com/lzlabs/pg_statemen= t_rollback/issues](https://github.com/lzlabs/pg_statement_rollback/issues) * Authors: [https://github.com/lzlabs/pg_statement_rollback/#authors](https= ://github.com/lzlabs/pg_statement_rollback/#authors) --===============8556133435148426556== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable pg_statement_rollback v1.5 released
 

pg_statement_rollback v1.5 released

Dar Es Salam - September 29th, 2025

Server side rollback at stateme= nt level for PostgreSQL

pg_statement_rollback is a PostgreSQL exten= sion to add server side transaction with rollback at statement level like in Oracle or DB2.

Release v1.5 of pg_statement_rollback was r= eleased. This is a maintenance release to add support to PostgreSQL 18.

See ChangeLog for a complete list of changes.

Links & Credits

pg_statement_rollback is an open project or= ignaly from LzLabs and now maintained by Gilles Darold at HexaCluster Corp/

Any contribution to build a better tool is = welcome. You just have to send your ideas, features requests or patches using the GitHub tools.

Links :
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/.
 
--===============8556133435148426556==-- --===============0430783575163792744==--