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.98.2) (envelope-from ) id 1xDXPS-00000000ZJV-3rt7 for pgsql-announce@arkaria.postgresql.org; Mon, 05 Oct 2026 01:22:31 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1xDXPR-00000006jGH-1bl1 for pgsql-announce@arkaria.postgresql.org; Mon, 05 Oct 2026 01:22:29 +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.98.2) (envelope-from ) id 1xDXKG-00000006RM2-3NXZ for pgsql-announce@lists.postgresql.org; Mon, 05 Oct 2026 01:17:08 +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 1xDXKD-00000000RSV-3GxB for pgsql-announce@lists.postgresql.org; Mon, 05 Oct 2026 01:17:08 +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=VsoNch5Pgon2xqobBvvet81L3ZOxRhrfOZzyMZ9tJOY=; b=29HsH61wlgukSQJ6ejpM1OpFlw bsBGZxcf2QRJQIlEHrE6TQvfLphOZmrbjHDrUY4kTIjOD5i/EHEkCjerepyHavHcDoEcm6sGIrT1c AmfTYjmfedpmRTQRSUg4V+s9VrkRYmRBVdqMrinauMSSErGMsDyf3S3HiD4eNAwPzT5zb0RxMMZ1H Ym4KQ21TykHR5JmBlSbx4daRH1TwYutjRUbPFeuAwRLUMiZ2L/vLxzw0pHBpTsjuwz2xCvS+kb8At TMEC/gNP7OccyCPmcgXZPDRGkX/hvXlimV4QAb8eohYILdeeQMWDbALdkKltj3NM+DIzCSzgH2pX2 dezmN1Xw==; 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.98.2) (envelope-from ) id 1xDXKC-00000001Izo-1na2 for pgsql-announce@lists.postgresql.org; Mon, 05 Oct 2026 01:17:04 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1xDXKB-00000003VM4-1KMJ for pgsql-announce@lists.postgresql.org; Mon, 05 Oct 2026 01:17:03 +0000 Content-Type: multipart/alternative; boundary="===============6645372147548037030==" MIME-Version: 1.0 Subject: pg_vault_tde v1.7.2 : Critical crash fixes, new on-disk format, and stability improvements To: PostgreSQL Announce From: Miriade Srl via PostgreSQL Announce Reply-To: marketing@miriade.it Date: Mon, 05 Oct 2026 01:16:05 +0000 Message-ID: <179116296516.1246.11337285365836705324@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-pglister-tags: related X-pglister-tagsig: f916705f3df07dc3aaeb7173a9300e54e84761f110da05e09144305e5771bc02 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --===============6645372147548037030== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Version 1.7.2 of `pg_vault_tde` is now available. This is a binary patch re= lease where extension version stays at 1.7, but users can distinguish the b= uild at runtime using `pg_vault_tde_build_version()`.=20 This update focuses on critical stability, security, and correctness fixes: * **New On-Disk Tuple Layout (v5)**: Introduces a walkable structure to f= ix a critical segmentation fault on `UPDATE` operations for tables with ind= exed variable-length columns (PSQLE-165). * **TOAST Crash Resolved**: Fixes a segfault triggered when values crosse= d the `TOAST_TUPLE_THRESHOLD` only after being encrypted. Furthermore, a bu= g where an all-NULL row made its table unreadable has been fixed. * **tde_btree Hardening**: The `tde_btree` index now strictly answers equ= ality queries only, preventing incorrect row returns on range operators, `O= RDER BY`, or merge joins (PSQLE-173). * **Key Management & Reliability**: Addresses data loss and corruption vu= lnerabilities in `rotate_online()` concurrent access (PSQLE-184), local wal= let KEK rotation (PSQLE-185), and vault-to-wallet migrations (PSQLE-188). * **WAL & Logical Decoding**: Fixes memory accounting drift in logical de= coding (PSQLE-186) and moves the Custom WAL resource manager ID from 128 to= the registered ID 161 (PSQLE-172). * **New script/checking improvement** : The development process now inclu= des ASan testing, Semgrep security checks, extended soak testing, and relea= se signing with a generated SBOM (PSQLE-180, PSQLE-181, PSQLE-182). **Critical Upgrade Instructions:** * Due to the WAL resource manager ID change, the upgrade requires a clean= shutdown. If `toast_custom_rmgr` is turned on, the primary and standbys mu= st be upgraded together, as a rolling upgrade is not possible. * Users **must** run `VACUUM FULL` on every encrypted table after the upg= rade. Existing rows in the v4 format remain readable but will crash on `UPD= ATE` until they are rewritten to the v5 layout. For a complete list of fixes and detailed upgrade procedures, please refer = to the ROADMAP.md file. --===============6645372147548037030== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable pg_vault_tde v1.7.2 : Critical crash fixes, new on-disk format, = and stability improvements
 

pg_vault_tde v1.7.2 : Critical crash fixes, new on-disk format, and s= tability improvements

Version 1.7.2 of pg_vault_tde = is now available. This is a binary patch release where extension version st= ays at 1.7, but users can distinguish the build at runtime using pg_v= ault_tde_build_version().

This update focuses on critical stability, = security, and correctness fixes:

  • New On-= Disk Tuple Layout (v5): Introduces a walkable structure to fix a c= ritical segmentation fault on UPDATE operations for tables wit= h indexed variable-length columns (PSQLE-165).
  • TOAST C= rash Resolved: Fixes a segfault triggered when values crossed the = TOAST_TUPLE_THRESHOLD only after being encrypted. Furthermore,= a bug where an all-NULL row made its table unreadable has been fixed.
  • tde_btr= ee Hardening: The tde_btree index now strictly answer= s equality queries only, preventing incorrect row returns on range operator= s, ORDER BY, or merge joins (PSQLE-173).
  • Key Man= agement & Reliability: Addresses data loss and corruption vuln= erabilities in rotate_online() concurrent access (PSQLE-184), = local wallet KEK rotation (PSQLE-185), and vault-to-wallet migrations (PSQL= E-188).
  • WAL &am= p; Logical Decoding: Fixes memory accounting drift in logical deco= ding (PSQLE-186) and moves the Custom WAL resource manager ID from 128 to t= he registered ID 161 (PSQLE-172).
  • New scr= ipt/checking improvement : The development process now includes AS= an testing, Semgrep security checks, extended soak testing, and release sig= ning with a generated SBOM (PSQLE-180, PSQLE-181, PSQLE-182).

Critical Upgrade Instructions:

  • Due to the WAL = resource manager ID change, the upgrade requires a clean shutdown. If toast_custom_rmgr is turned on, the primary and standbys must be up= graded together, as a rolling upgrade is not possible.
  • Users m= ust run VACUUM FULL on every encrypted table after th= e upgrade. Existing rows in the v4 format remain readable but will crash on= UPDATE until they are rewritten to the v5 layout.

For a complete list of fixes and detailed u= pgrade procedures, please refer to the ROADMAP.md file.
This email was sent to you from Miriade Srl. It was delivered on their beha= lf by the PostgreSQL project. Any questions about the content of the message shou= ld be sent to Miriade Srl.

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/.
 
--===============6645372147548037030==--