| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: better page-level checksums |
| Date: | 2022-06-13 22:06:14 |
| Message-ID: | Yqe01lndDG4G1Jjz@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jun 13, 2022 at 03:03:17PM -0700, Peter Geoghegan wrote:
> On Mon, Jun 13, 2022 at 2:54 PM Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> > On Mon, Jun 13, 2022 at 02:44:41PM -0700, Peter Geoghegan wrote:
> > > Is that the how block-level encryption feature from EDB Advanced Server does it?
> >
> > Uh, EDB Advanced Server doesn't have a block-level encryption feature.
>
> Apparently there is something called "Vormetric Transparent Encryption
> (VTE) – Transparent block-level encryption with access controls":
>
> https://www.enterprisedb.com/blog/enhanced-security-edb-postgres-advanced-server-vormetric-data-security-platform
>
> Perhaps there is some kind of confusion around the terminology here?
That is encryption done in a virtual file system independent of
Postgres. So, I guess the answer to your question is that this is not
how EDB Advanced Server does it.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Indecision is a decision. Inaction is an action. Mark Batterson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Zhang | 2022-06-13 22:18:45 | Re: Non-replayable WAL records through overflows and >MaxAllocSize lengths |
| Previous Message | Peter Geoghegan | 2022-06-13 22:03:17 | Re: better page-level checksums |