From: Thorsten Glaser <tg@evolvis.org>
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 20:02:35 +0200 (CEST)
Message-ID: <e46cf66d-4ccc-e6f6-4772-4b671192f243@evolvis.org> (raw)
In-Reply-To: <CACufLfzWQT9sQ6eaycvzehV76OeWKTtG7FTv5LVxpAEgJR7f4Q@mail.gmail.com>
References: <CACufLfw0y3v1kfz-OVP5OupP_b5sei-x_gfh16Lx=Pgd6jehrQ@mail.gmail.com>
<ZGZKN0fQORPPNqc5@tamriel.snowman.net>
<CACufLfzWQT9sQ6eaycvzehV76OeWKTtG7FTv5LVxpAEgJR7f4Q@mail.gmail.com>
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?
Better isolation of the customers, but still on one server.
bye,
//mirabilos
--
15:41⎜<Lo-lan-do:#fusionforge> Somebody write a testsuite for helloworld :-)
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: tg@evolvis.org, tony.xu@rubrik.com
Subject: Re: Would PostgreSQL 16 native transparent data encryption support database level encryption?
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>
* 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