pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Christophe Pettus <xof@thebuild.com>
To: Tony Xu <tony.xu@rubrik.com>
Cc: pgsql-generallists.postgresql.org <pgsql-general@lists.postgresql.org>
Subject: Re: Would PostgreSQL 16 native transparent data encryption support database level encryption?
Date: Mon, 22 May 2023 11:16:20 -0700
Message-ID: <78CFAEC1-8D31-4CF6-AAFE-AE6C34AD0F42@thebuild.com> (raw)
In-Reply-To: <CACufLfwDbvsF9d_AxZb1Co0SJJB2XnCYuwQ5+FhVtGF3VYBQmg@mail.gmail.com>
References: <CACufLfw0y3v1kfz-OVP5OupP_b5sei-x_gfh16Lx=Pgd6jehrQ@mail.gmail.com>
	<ZGZKN0fQORPPNqc5@tamriel.snowman.net>
	<08c133e0-b136-ff80-886e-b0d4f621c75c@gmail.com>
	<f714e518-374a-8d74-1119-9a363857a367@gmail.com>
	<1d0735cf-b5dd-1c05-d03a-9b52ee2cc5bb@gmail.com>
	<5d617fb4-a2de-f6a2-f0d3-8a068ac4d83f@aklaver.com>
	<CADX_1abemND-2kO4sc8erSTr=WdP96Wp2onZfKbE2f+VYrP4CA@mail.gmail.com>
	<a3a68610-1b16-1ef5-11cd-2d191faec868@gmx.net>
	<CADX_1abAcP60kOA2U-b4oj5KGgJqSoLxYDR731L2YHcANZsNEw@mail.gmail.com>
	<CACufLfwDbvsF9d_AxZb1Co0SJJB2XnCYuwQ5+FhVtGF3VYBQmg@mail.gmail.com>



> On May 22, 2023, at 11:02, Tony Xu <tony.xu@rubrik.com> wrote:
> there are still some shared area between clusters.

That's not quite right.  A PostgreSQL cluster (in the traditional sense, which means one PostgreSQL server handling a particular endpoint) is isolated from any other clusters on the same machine.  If the individual clusters have their own underlying volumes, those can be encrypted independently of any other cluster.  This is not quite as elegant as each database in a cluster having its own encryption key, but it does have the advantage that it can be deployed right now.

A single cluster does have shared areas between databases, and those are not trivial: The global system catalogs, the write-ahead log, and the commit log, just for a start.  The global system catalogs include users and roles.  The effort required to split those up is very significant.

And, to be somewhat blunt, is Rubrik prepared to pay for it?  This engineering effort needs to be funded by someone, since engineers have to eat.  This is not to say that any feature someone is willing to pay for will make it into PostgreSQL, but an effort of this size, to have any hope of reaching the point of being accepted, will need someone to pay the salaries of the people working on it.

Best,
-- Christophe




view thread (36+ messages)  latest in thread

Message-ID: <78CFAEC1-8D31-4CF6-AAFE-AE6C34AD0F42@thebuild.com>
Permalink:  ../78CFAEC1-8D31-4CF6-AAFE-AE6C34AD0F42@thebuild.com/
Also on:    postgresql.org/message-id/78CFAEC1-8D31-4CF6-AAFE-AE6C34AD0F42@thebuild.com

 · 

reply

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: xof@thebuild.com, tony.xu@rubrik.com
  Subject: Re: Would PostgreSQL 16 native transparent data encryption support database level encryption?
  In-Reply-To: <78CFAEC1-8D31-4CF6-AAFE-AE6C34AD0F42@thebuild.com>
  References: <CACufLfw0y3v1kfz-OVP5OupP_b5sei-x_gfh16Lx=Pgd6jehrQ@mail.gmail.com> <ZGZKN0fQORPPNqc5@tamriel.snowman.net> <08c133e0-b136-ff80-886e-b0d4f621c75c@gmail.com> <f714e518-374a-8d74-1119-9a363857a367@gmail.com> <1d0735cf-b5dd-1c05-d03a-9b52ee2cc5bb@gmail.com> <5d617fb4-a2de-f6a2-f0d3-8a068ac4d83f@aklaver.com> <CADX_1abemND-2kO4sc8erSTr=WdP96Wp2onZfKbE2f+VYrP4CA@mail.gmail.com> <a3a68610-1b16-1ef5-11cd-2d191faec868@gmx.net> <CADX_1abAcP60kOA2U-b4oj5KGgJqSoLxYDR731L2YHcANZsNEw@mail.gmail.com> <CACufLfwDbvsF9d_AxZb1Co0SJJB2XnCYuwQ5+FhVtGF3VYBQmg@mail.gmail.com> <78CFAEC1-8D31-4CF6-AAFE-AE6C34AD0F42@thebuild.com>

* 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