| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Enquiry about TDE with PgSQL |
| Date: | 2025-10-30 19:59:58 |
| Message-ID: | aQPDvqUzZVKkaxsS@momjian.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Oct 17, 2025 at 09:01:52AM +0200, Laurenz Albe wrote:
> On Fri, 2025-10-17 at 00:49 -0400, Ron Johnson wrote:
> > On Thu, Oct 16, 2025 at 6:05 PM Greg Sabino Mullane <htamfids(at)gmail(dot)com> wrote:
> > >
> > > TDE, on the other hand, is a very complex and difficult thing to add into Postgres.
> >
> > TDE was added to SQL Server, with (to us, at least) minimally-noticed overhead.
> > Oracle has it, too, but I don't know the details.
> >
> > The bottom line is that requirements for TDE are escalating, whether you like it or
> > not, as Yet Another Layer Of Defense against hackers exfiltrating data, and then
> > threatening to leak it to the public.
>
> Bruce Momjian has interesting things to say about that in
> https://compiledconversations.com/6/ (unfortunately I don't remember where
> exactly in this 84 minute piece).
Here is my most recent blog about TDE:
https://momjian.us/main/blogs/pgblog/2025.html#February_22_2025
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Do not let urgent matters crowd out time for investment in the future.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | DINESH NAIR | 2025-10-31 06:38:54 | Re: Why isn't my table auto-analyzed/vacuumed? |
| Previous Message | Ron Johnson | 2025-10-30 18:46:17 | Re: Why isn't my table auto-analyzed/vacuumed? |