From: Stephen Frost <sfrost@snowman.net>
To: Tony Xu <tony.xu@rubrik.com>
Cc: pgsql-general@postgresql.org
Subject: Re: Would PostgreSQL 16 native transparent data encryption support database level encryption?
Date: Thu, 18 May 2023 19:47:00 -0400
Message-ID: <ZGa49CRDJoIfWa/a@tamriel.snowman.net> (raw)
In-Reply-To: <CACufLfzuKODFu4yyz1ZFkn7ThkhPmYrc=D2b_hhMhwz5NVaC2Q@mail.gmail.com>
References: <CACufLfw0y3v1kfz-OVP5OupP_b5sei-x_gfh16Lx=Pgd6jehrQ@mail.gmail.com>
<ZGZKN0fQORPPNqc5@tamriel.snowman.net>
<CACufLfzWQT9sQ6eaycvzehV76OeWKTtG7FTv5LVxpAEgJR7f4Q@mail.gmail.com>
<ZGasXpzeKnxwk3Hn@tamriel.snowman.net>
<CACufLfzuKODFu4yyz1ZFkn7ThkhPmYrc=D2b_hhMhwz5NVaC2Q@mail.gmail.com>
Greetings,
Really, please don't top-post on these lists.
* Tony Xu (tony.xu@rubrik.com) wrote:
> Regarding the multiple clusters idea, how does that work? Assume we can
> store one customer's data in one cluster, is it possible to have separate
> KEK for different clusters?
In the proposed TDE work, yes, each cluster (which is an entier
PostgreSQL system) would be able to have its own KEK.
> Why not using multiple clusters then?
There's a bit of overhead from each cluster and each would have their
own shared buffers pool of memory and such.
> Better isolation of the customers, but still on one server.
Depending on the OS, multi-cluster management on a given system is
easier or harder. In my view, at least, Debian systems make having
multiple clusters on a given server a lot easier as they have
pg_createcluster, pg_lsclusters, etc, commands and management tools.
Another alternative would be to use container technology and Kubernetes
or OpenShift and a PG Operator to manage all the clusters across
whatever systems you're running on top of.
Of course, there are trade-offs to consider between all of these
different approaches.
Thanks,
Stephen
Attachments:
signature.asc (application/pgp-signature, 832B) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: sfrost@snowman.net, tony.xu@rubrik.com
Subject: Re: Would PostgreSQL 16 native transparent data encryption support database level encryption?
In-Reply-To: <ZGa49CRDJoIfWa/a@tamriel.snowman.net>
References: <CACufLfw0y3v1kfz-OVP5OupP_b5sei-x_gfh16Lx=Pgd6jehrQ@mail.gmail.com> <ZGZKN0fQORPPNqc5@tamriel.snowman.net> <CACufLfzWQT9sQ6eaycvzehV76OeWKTtG7FTv5LVxpAEgJR7f4Q@mail.gmail.com> <ZGasXpzeKnxwk3Hn@tamriel.snowman.net> <CACufLfzuKODFu4yyz1ZFkn7ThkhPmYrc=D2b_hhMhwz5NVaC2Q@mail.gmail.com> <ZGa49CRDJoIfWa/a@tamriel.snowman.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox