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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Thorsten Glaser <tg(at)evolvis(dot)org>
Cc: 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 18:23:17
Message-ID: 3867047.1684434197@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Thorsten Glaser <tg(at)evolvis(dot)org> writes:
> On Thu, 18 May 2023, Tony Xu wrote:
>> Our use-case is for a multi-tenancy scenario - we are considering using
>> different databases to store different customer's data, however, for

> Why not using multiple clusters then?

Yeah. The problem with key-per-database is what are you going to do
with the shared catalogs? It's a lot simpler, and probably better
performing, to use one key per cluster.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Ron 2023-05-18 18:51:10 Re: Would PostgreSQL 16 native transparent data encryption support database level encryption?
Previous Message Tom Lane 2023-05-18 18:20:13 Re: Unrecognized Node Type Warning