From: Tom Lane <tgl@sss.pgh.pa.us>
To: Thorsten Glaser <tg@evolvis.org>
Cc: 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 14:23:17 -0400
Message-ID: <3867047.1684434197@sss.pgh.pa.us> (raw)
In-Reply-To: <e46cf66d-4ccc-e6f6-4772-4b671192f243@evolvis.org>
References: <CACufLfw0y3v1kfz-OVP5OupP_b5sei-x_gfh16Lx=Pgd6jehrQ@mail.gmail.com>
<ZGZKN0fQORPPNqc5@tamriel.snowman.net>
<CACufLfzWQT9sQ6eaycvzehV76OeWKTtG7FTv5LVxpAEgJR7f4Q@mail.gmail.com>
<e46cf66d-4ccc-e6f6-4772-4b671192f243@evolvis.org>
Thorsten Glaser <tg@evolvis.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
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: tgl@sss.pgh.pa.us, tg@evolvis.org, tony.xu@rubrik.com
Subject: Re: Would PostgreSQL 16 native transparent data encryption support database level encryption?
In-Reply-To: <3867047.1684434197@sss.pgh.pa.us>
References: <CACufLfw0y3v1kfz-OVP5OupP_b5sei-x_gfh16Lx=Pgd6jehrQ@mail.gmail.com> <ZGZKN0fQORPPNqc5@tamriel.snowman.net> <CACufLfzWQT9sQ6eaycvzehV76OeWKTtG7FTv5LVxpAEgJR7f4Q@mail.gmail.com> <e46cf66d-4ccc-e6f6-4772-4b671192f243@evolvis.org> <3867047.1684434197@sss.pgh.pa.us>
* 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