Re: Transparent column encryption

From: Andres Freund <andres(at)anarazel(dot)de>
To: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Transparent column encryption
Date: 2023-03-12 00:11:25
Message-ID: 20230312001125.ijeu4imbwlhj5flf@awork3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 2023-03-10 08:18:34 +0100, Peter Eisentraut wrote:
> Here is an updated patch. I have done some cosmetic polishing and fixed a
> minor Windows-related bug.
>
> In my mind, the patch is complete.
>
> If someone wants to do some in-depth code review, I suggest focusing on the
> following files:
>
> * src/backend/access/common/printtup.c

Have you done benchmarks of some simple workloads to verify this doesn't cause
slowdowns (when not using encryption, obviously)? printtup.c is a performance
sensitive portion for simple queries, particularly when they return multiple
columns.

And making tupledescs even wider is likely to have some price, both due to the
increase in memory usage, and due to the lower cache density - and that's code
where we're already hurting noticeably.

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2023-03-12 00:12:21 Re: unsafe_tests module
Previous Message Imseih (AWS), Sami 2023-03-11 23:55:22 Re: [BUG] pg_stat_statements and extended query protocol