From: | Andreas Kretschmer <andreas(at)a-kretschmer(dot)de> |
---|---|
To: | pgsql-general(at)lists(dot)postgresql(dot)org, Ron <ronljohnsonjr(at)gmail(dot)com> |
Subject: | Re: Will PostgreSQL 16 supports native transparent data encryption ? |
Date: | 2023-08-22 05:18:56 |
Message-ID: | EE6FEBF0-D029-4967-A824-57A59425BF87@a-kretschmer.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 22 August 2023 06:52:10 CEST, Ron <ronljohnsonjr(at)gmail(dot)com> wrote:
>On 8/21/23 18:49, Bruce Momjian wrote:
>> On Mon, Aug 21, 2023 at 07:02:46PM +0300, Mostafa Fathy wrote:
>>> Hi there,
>>>
>>> It is mentioned here https://www.postgresql.org/about/press/faq/#:~:text=
>>> Q%3A%20What%20features%20will%20PostgreSQL%2016%20have%3F that native
>>> transparent data encryption is being worked on and it may be delivered with
>>> PostgreSQL 16.
>>>
>>> Is PostgreSQL 16 beta version includes native transparent data encryption or
>>> not ? because I checked the docs https://www.postgresql.org/docs/16/index.html
>>> and couldn't find anything related to transparent data encryption.
>>>
>>> If not supported yet in the beta version I would like to know if PostgreSQL 16
>>> final version will support native transparent data encryption or not?
>> Not, PG 16 will not support it, and I am unclear if later major versions
>> will either.
>
>That's disappointing, since TDE makes PCI audits that much simpler.
>
Sure. You can use EDB products (EPAS or Postgres Extended) with TDE.
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Edoardo Panfili | 2023-08-22 05:54:15 | Re: The same prepared query yield "-1" the first six times and then "-1.0" |
Previous Message | David G. Johnston | 2023-08-22 05:06:44 | Re: EXPLAIN statement can also apply to SELECT INTO. |