| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | David Christensen <david(dot)christensen(at)crunchydata(dot)com> |
| Cc: | vignesh C <vignesh21(at)gmail(dot)com>, Aleksander Alekseev <aleksander(at)timescale(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Stephen Frost <sfrost(at)snowman(dot)net> |
| Subject: | Re: Moving forward with TDE [PATCH v3] |
| Date: | 2023-11-04 02:53:14 |
| Message-ID: | 20231104025314.klj7kxucielpviwn@awork3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2023-11-02 19:32:28 -0700, Andres Freund wrote:
> > From 327e86d52be1df8de9c3a324cb06b85ba5db9604 Mon Sep 17 00:00:00 2001
> > From: David Christensen <david(at)pgguru(dot)net>
> > Date: Fri, 29 Sep 2023 15:16:00 -0400
> > Subject: [PATCH v3 5/5] Add encrypted/authenticated WAL
> >
> > When using an encrypted cluster, we need to ensure that the WAL is also
> > encrypted. While we could go with an page-based approach, we use instead a
> > per-record approach, using GCM for the encryption method and storing the AuthTag
> > in the xl_crc field.
What was the reason for this decision?
?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2023-11-04 04:19:00 | Re: Add the ability to limit the amount of memory that can be allocated to backends. |
| Previous Message | David Rowley | 2023-11-04 02:43:34 | Re: Pre-proposal: unicode normalized text |