From: | Andreas Kretschmer <andreas(at)a-kretschmer(dot)de> |
---|---|
To: | pgsql-general(at)lists(dot)postgresql(dot)org, Tony Xu <tony(dot)xu(at)rubrik(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Would PostgreSQL 16 native transparent data encryption support database level encryption? |
Date: | 2023-05-18 09:31:08 |
Message-ID: | B19E28C6-F582-4962-8C59-203F6A33BE47@a-kretschmer.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
It is in epas15, but for the whole cluster. Different keys for each database is not possible, how should it works for instance the wal - stream?
On 18 May 2023 00:35:39 CEST, Tony Xu <tony(dot)xu(at)rubrik(dot)com> wrote:
>Hi There,
>
>The FAQ (copied below) mentioned that native transparent data encryption
>might be included in 16. Is it fair to assume that it will support database
>level encryption, that is, we can use two encryption keys for two databases
>in the same server, respectively? How can one verify that?
>
>Thanks
>Tony
>
>
>
>
>*https://www.postgresql.org/about/press/faq/
><https://www.postgresql.org/about/press/faq/>*
>
>*Q: What features will PostgreSQL 16 have?A: As always, we can't be certain
>what will go in and what won't; the project has strict quality standards
>that not all patches can make before deadline. All we can tell you is
>what's currently being worked on, which includes native transparent data
>encryption support, continued improvements to logical replication,
>parallelism, partitioning, and vacuuming, and many more features. By the
>time 16 is released, though, this list may have changed considerably.*
From | Date | Subject | |
---|---|---|---|
Next Message | Victor Nordam Suadicani | 2023-05-18 12:27:27 | Is there a good way to handle sum types (or tagged unions) in PostgreSQL? |
Previous Message | Tony Xu | 2023-05-18 05:27:54 | Re: Would PostgreSQL 16 native transparent data encryption support database level encryption? |