| 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-13 20:41:19 |
| Message-ID: | 20230313204119.4mkepdvixcxrwpsc@awork3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2023-03-13 21:22:29 +0100, Peter Eisentraut wrote:
> On 12.03.23 01:11, Andres Freund wrote:
> > 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.
>
> The additional code isn't used when column encryption is off, so there
> shouldn't be any impact.
It adds branches, and it makes tupledescs wider. In tight spots, such as
printtup, that can hurt, even if the branches aren't ever entered.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nazir Bilal Yavuz | 2023-03-13 20:46:41 | Re: meson: Non-feature feature options |
| Previous Message | Stephen Frost | 2023-03-13 20:33:31 | Re: Improve logging when using Huge Pages |