pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-general@lists.postgresql.org
Subject: Re: Would PostgreSQL 16 native transparent data encryption support database level encryption?
Date: Mon, 22 May 2023 14:38:39 -0500
Message-ID: <fc6caca1-017e-3691-0375-ede50cadc89c@gmail.com> (raw)
In-Reply-To: <CACufLfxmdhgth+2J7jEktkqjMDHKVhDdzZtJERiOnAd9Md8sSA@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>
	<78CFAEC1-8D31-4CF6-AAFE-AE6C34AD0F42@thebuild.com>
	<CACufLfxmdhgth+2J7jEktkqjMDHKVhDdzZtJERiOnAd9Md8sSA@mail.gmail.com>

On 5/22/23 14:22, Tony Xu wrote:
> Thanks Christophe for the clarification.
>
>     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.
>
>
> Thanks. I think I had a misunderstanding over the "cluster" eariler. So a 
> PostgreSQL cluster is a PostgreSQL server that we're talking about in 
> general. This means per-DB KEY within a cluster/server is impossible 
> without splitting the whole shared storage among databases, which is 
> indeed a significant amount of work.

"Cluster" is to Postgres as "Instance" is to SQL Server

>     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.
>
> I cannot speak on behalf of Rubrik - I'm just exploring PostgreSQL as a 
> solution for one of my team's projects thus the questions. Nothing is 
> finalized yet but we prefer a managed solution provided by some cloud 
> infra providers so the context I'm getting here will allow me to better 
> understand our provider's solution and their road map.

RDS Postgresql would do the job just fine.  And since you can't get to the 
files (only access it via port 5432 and aws cli/web, there's no need for TDE.

Azure is probably the same.

-- 
Born in Arizona, moved to Babylonia.

view thread (36+ messages)  latest in thread

Message-ID: <fc6caca1-017e-3691-0375-ede50cadc89c@gmail.com>
Permalink:  ../fc6caca1-017e-3691-0375-ede50cadc89c@gmail.com/
Also on:    postgresql.org/message-id/fc6caca1-017e-3691-0375-ede50cadc89c@gmail.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: ronljohnsonjr@gmail.com
  Subject: Re: Would PostgreSQL 16 native transparent data encryption support database level encryption?
  In-Reply-To: <fc6caca1-017e-3691-0375-ede50cadc89c@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> <78CFAEC1-8D31-4CF6-AAFE-AE6C34AD0F42@thebuild.com> <CACufLfxmdhgth+2J7jEktkqjMDHKVhDdzZtJERiOnAd9Md8sSA@mail.gmail.com> <fc6caca1-017e-3691-0375-ede50cadc89c@gmail.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