Re: Would PostgreSQL 16 native transparent data encryption support database level encryption?

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Tony Xu <tony(dot)xu(at)rubrik(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Would PostgreSQL 16 native transparent data encryption support database level encryption?
Date: 2023-05-18 15:54:31
Message-ID: ZGZKN0fQORPPNqc5@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Greetings,

* Tony Xu (tony(dot)xu(at)rubrik(dot)com) wrote:
> 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?

The current work to include TDE in PG isn't contemplating a per-database
key option. What's the use-case for that? Why do you feel that you'd
need two independent keys? Also, the general idea currently is that
we'll have one key provided by the user which will be a KEK and then
multiple DEKs (different ones for relation data vs. temporary data vs.
the WAL).

If you're interested in TDE in PG, we could certainly use more folks
being involved and working to push it forward.

Thanks,

Stephen

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2023-05-18 15:57:49 Re: JSONB operator unanticipated behaviour
Previous Message Tom Lane 2023-05-18 15:46:53 Re: JSONB operator unanticipated behaviour