Re: Transparent column encryption

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Transparent column encryption
Date: 2024-04-10 10:12:52
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

To kick some things off for PG18, here is an updated version of the
patch for automatic client-side column-level encryption. (See commit
message included in the patch for a detailed description, if you have
forgotten. Also, see [0] if the thread has dropped off your local mail


This patch got stuck around CF 2023-03 because expanding the size of the
tuple descriptor (with new pg_attribute columns) had a noticeable
performance impact. Various work in PG17 has made it more manageable to
have columns in pg_attribute that are not in the tuple descriptor, and
this patch now takes advantage of that (and I wanted to do this merge
soon to verify that the changes in PG17 are usable). Otherwise, this
version v20 is functionally unchanged over the last posted version v19.
Obviously, it's early days, so there will be plenty of time to have
discussions on various other aspects of this patch. I'm keeping a keen
eye on the discussion of protocol extensions, for example.

Attachment Content-Type Size
v20-0001-Automatic-client-side-column-level-encryption.patch text/plain 478.6 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2024-04-10 10:21:04 Re: Potential stack overflow in incremental base backup
Previous Message Tender Wang 2024-04-10 10:11:02 Re: Can't find not null constraint, but \d+ shows that