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 1vFV7G-00CW18-I8 for pgsql-general@arkaria.postgresql.org; Sun, 02 Nov 2025 10:15:18 +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 1vFV7F-00ARhx-E1 for pgsql-general@arkaria.postgresql.org; Sun, 02 Nov 2025 10:15:16 +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 1vFV7F-00ARhp-0h for pgsql-general@lists.postgresql.org; Sun, 02 Nov 2025 10:15:16 +0000 Received: from mail-qt1-x836.google.com ([2607:f8b0:4864:20::836]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1vFV7A-005Ya5-22 for pgsql-general@postgresql.org; Sun, 02 Nov 2025 10:15:15 +0000 Received: by mail-qt1-x836.google.com with SMTP id d75a77b69052e-4e88cacc5d9so34580221cf.0 for ; Sun, 02 Nov 2025 02:15:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=percona.com; s=google; t=1762078510; x=1762683310; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=nLONcDFO+NfJ7QgJTF2+rFXYwKIVSkqM1iPoP7DXU88=; b=TOgtmcVW2BaesojwEpipTCocpyUvifk/TO0ysD1EOFPKIPrsFsWXvLxPncAfuI/+L/ ycB8Mq7mxzj8wzWbtrajb3lwduiCvhrcinr88XQ9JwSEUcYnDeOux+VJ+tqv7nKfpmGU Av91cfvibdCskKZ2x+FOTh2CQ9r9hTMl9cNns= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1762078510; x=1762683310; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=nLONcDFO+NfJ7QgJTF2+rFXYwKIVSkqM1iPoP7DXU88=; b=B7WhdpKglgotjqMl2EmTX+SM++igkM9tBFCUbvZ+u0KocLF6dJFrwtH89/hypPWPvv 6yxMauV3FwIgFx9NiqQTs7hzDdYC2+Pm07Njr1A19K2xhI4lBMwkx30ksHD9gaL9i6fD YUdcU8gAL/Ak2m28AlKmqarE45ocejql37xzymOlCdFt2RlEt03VB9WgokqEBhRowgZM ovS+ZTV1WXc/ERM/qHeCbvQGsky3LgZ7YcQVhJDWFkXTwxUcR1OGpHjVuNcjzD5WiAHM u8o4qVtytOcHq19Ndj732ISfLjjPZWtq+8vC7GMu/xD/Bs4tRIkTv2PuEpYdTnjJSyPb X86g== X-Forwarded-Encrypted: i=1; AJvYcCWs10QSBTa76OO0QyP27psm+lUO09X5n1lSWrE8zal0QTO3AOKUff/eJelyDBvwYk2EoUaOlZxhrvYOt/yk@postgresql.org X-Gm-Message-State: AOJu0YxZIJnv4TNP2lEC9S7SUGeVEXfYzM6Ux8FZ3bYp/hJHW+S1jlru 4lM8I1rPxlge8qWO3YcRMr6KQtNjNWa95gE3PlkqZryOvI5BUUH5hgHS8QAsik2S2Rmy6n9ew/I ceT1mbMnFQEjEBCv6C79emh0omoR+58IinFX3W+4NMCwkjULZmawZJRK9RZoiK7Su748pJiFihg wt9NOh54rZItsPYBOiECWa6szn5ezg3Bcjt79Ci2B9/DRoiKDagjvEb5LOZIvTNBabcQEbQeXHr 04vs7lkdvAkAqikJIv97hT3wq9KZRtTUlFiBxTOJK4pb00GdoA= X-Gm-Gg: ASbGnctQ/AbtBIULOsHAad/A7bC8/0+8Q3DJR08kWmALilbADzralNL5sx9p5mU4y4K WudURidpSTh98Tao/rMu8qXQWlseSyoNH9g7dSsG208EhMADQBZ67XEXLyWviyYv2XD0fEkLIFa AZLzLKTqCTP//j+xa/eovnOYg3VUpuYWm0DgJx7aqOJIGKxiKETivrb3ZDeGzKlZgb5LdVGuaAp 7aqhc2z6bn7G8W92eZ7GAus7o3kmNmN0O+14DW2ukrQkZ0EcfMHcxMvCQLTAwRHIGpiIQH/13PZ GqR1EUI= X-Google-Smtp-Source: AGHT+IEyeIhaorkB42ZBBk333UtxYYmkO181J3Nj57w3S9SwKR1koWalog5ZBNIs5ECh6Aw4VGFf4YmwVe4RI0s1ySA= X-Received: by 2002:a05:622a:5a0a:b0:4ec:f23c:3b94 with SMTP id d75a77b69052e-4ed30e13600mr124963471cf.36.1762078509486; Sun, 02 Nov 2025 02:15:09 -0800 (PST) MIME-Version: 1.0 References: <3DC589BC-A5F6-49BC-BFFC-F1FCB0FF7E95@thebuild.com> In-Reply-To: From: Kai Wagner Date: Sun, 2 Nov 2025 11:14:58 +0100 X-Gm-Features: AWmQ_bm9OSLm4_nkN7DZrDmW6V_XPBMz992KJeTiYyUjD9f1Y1GM_BRabPaHZQM Message-ID: Subject: Re: Enquiry about TDE with PgSQL To: Bruce Momjian Cc: Chris Travers , Christophe Pettus , "Clay Jackson (cjackson)" , pgsql-general , Laurenz Albe , Ron Johnson Content-Type: multipart/alternative; boundary="0000000000009fe592064299df72" X-CLOUD-SEC-AV-Sent: true X-CLOUD-SEC-AV-Info: percona,google_mail,monitor X-Gm-Spam: 0 X-Gm-Phishy: 0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000009fe592064299df72 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sat, Nov 1, 2025 at 2:58=E2=80=AFPM Bruce Momjian wro= te: > If you want to move forward with TDE without waiting to see if the > temporary file compression patch will reduce the TDE code impact, you > need to dig into how the community does feature calculus and how that > calculus can be changed --- this is not something technology can fix. > I fully agree here, and as I stated above, I don't question this at all, as this is the strength of the diverse and spread community. Looking at this thread alone, and the multiple different "users" popping up, that see the need and would like to see TDE in core or in an extension drives my thinking as it makes sense to start thinking and looking into the temp file compression already right now, if and how this could make our code changes easier, or if additional extensibility should be directly part of the first patch, so you can enable it through its extension. Either way, it should be considered and kept in mind now, not after the fact, or we will continue to spin this wheel. And this thinking and willingness alone, to actually be open to that idea, requires some upfront discussion, so you at least know you are welcome to work on it without wasting effort, because no one will ever want to merge. (and yes, of course everyone can work on whatever they want at any point in time, but people might prefer working on something that actually benefits the project and is welcome, rather than ending in >/dev/null) Given your experience Bruce, can you offer us some advice on how you would approach it currently? What do you think makes the most sense, and how should we proceed with collaboration to at least see a small change in making this happen in the future? > > Companies are willing to add the code weight because it is a sale for > them, and customers are willing to pay to meet the check box --- that > calculus just doesn't work in the community. > And this should always be at the forefront, as this makes the project exactly as strong as it is today. > > -- > Bruce Momjian > https://url.avanan.click/v2/r01/___https://momjian.us___.YXAzOnBlcmNvbmE6= YTpnOmZhM2VjN2JlNjcyOTZmMGQwMjEzOGM1NWU5OTA5NzM0Ojc6ZDgxOTo3NzQ0MzQwZjhmODA= 4YmY1ZjFiZmFlMzdlNmE4MzUxYzc0NGU0NTIwMjA5YWU1Mjk2NjQ5YjFiZjk0NDI3MDNjOnA6VD= pO > EDB > https://url.avanan.click/v2/r01/___https://enterprisedb.com___.YXAzOnBlcm= NvbmE6YTpnOmZhM2VjN2JlNjcyOTZmMGQwMjEzOGM1NWU5OTA5NzM0Ojc6MjZhZTplMDhhZWQ5N= zg3YmVjODI4MDQ5YmU2ODc1MGExMTVmMmRmOTVlOTk2N2FmM2Y1N2VkN2VmYTZhYWMyZDQ1MzE3= OnA6VDpO > > Do not let urgent matters crowd out time for investment in the future. > --0000000000009fe592064299df72 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Sat, Nov 1, 2025 at 2:58=E2=80=AFPM Br= uce Momjian <bruce@momjian.us>= ; wrote:
If you want to move forward with TDE = without waiting to see if the
temporary file compression patch will reduce the TDE code impact, you
need to dig into how the community does feature calculus and how that
calculus can be changed --- this is not something technology can fix.
I fully agree here, and as I stated above, I don't ques= tion this at all, as this is the strength of the diverse and spread communi= ty. Looking at this thread alone, and the multiple different "users&qu= ot; popping up, that see the need and would like to see TDE in core or in a= n extension drives my thinking as it makes sense to start thinking and look= ing into the temp file compression already right now, if and how this could= make our code changes easier, or if additional extensibility should be dir= ectly part of the first patch, so you can enable it through its extension.= =C2=A0Either way, it should be considered and kept in mind now, not after t= he fact, or we will continue to spin this wheel. And this thinking and will= ingness alone, to actually be open to that idea, requires some upfront disc= ussion, so you at least know you are welcome to work on it without wasting = effort, because no one will ever want to merge. (and yes, of course everyon= e can work on whatever they want at any point in time, but people might pre= fer working on something that actually benefits the project and is welcome,= rather than ending in >/dev/null)

Given your e= xperience Bruce, can you offer us some advice on how you would approach it = currently? What do you think makes the most sense, and how should we procee= d with collaboration to at least see a small change in making this happen i= n the future?=C2=A0

Companies are willing to add the code weight because it is a sale for
them, and customers are willing to pay to meet the check box --- that
calculus just doesn't work in the community.
And t= his should always be at the forefront, as this makes the project exactly as= strong as it is today.=C2=A0=C2=A0

--
=C2=A0 Bruce Momjian=C2=A0 <bruce@momjian.us>=C2=A0 =C2=A0 =C2=A0 =C2=A0 https://url.avanan.click/v2/r01/___h= ttps://momjian.us___.YXAzOnBlcmNvbmE6YTpnOmZhM2VjN2JlNjcyOTZmMGQwMjEzOGM1NW= U5OTA5NzM0Ojc6ZDgxOTo3NzQ0MzQwZjhmODA4YmY1ZjFiZmFlMzdlNmE4MzUxYzc0NGU0NTIwM= jA5YWU1Mjk2NjQ5YjFiZjk0NDI3MDNjOnA6VDpO
=C2=A0 EDB=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 https://url.avanan.click= /v2/r01/___https://enterprisedb.com___.YXAzOnBlcmNvbmE6YTpnOmZhM2VjN2JlNjcy= OTZmMGQwMjEzOGM1NWU5OTA5NzM0Ojc6MjZhZTplMDhhZWQ5Nzg3YmVjODI4MDQ5YmU2ODc1MGE= xMTVmMmRmOTVlOTk2N2FmM2Y1N2VkN2VmYTZhYWMyZDQ1MzE3OnA6VDpO

=C2=A0 Do not let urgent matters crowd out time for investment in the futur= e.
--0000000000009fe592064299df72--