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: Thu, 18 May 2023 14:45:56 -0500
Message-ID: <b31d1248-7307-0b4e-38cc-2d8ff51c3b90@gmail.com> (raw)
In-Reply-To: <d22f21d-e256-15aa-9d79-68522af2edd0@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>
<7636ea3e-fab7-1681-4e7e-464faa2d127f@gmail.com>
<d22f21d-e256-15aa-9d79-68522af2edd0@evolvis.org>
On 5/18/23 14:07, Thorsten Glaser wrote:
> On Thu, 18 May 2023, Ron wrote:
>
>>> Why not using multiple clusters then?
>> Yet More Firewall Rules to get approved by the Security Team. And then they
>> balk at port 5433 because they've never heard of it.
> But mixing multiple customers on one cluster is much more of a risk.
Better have your roles and pg_hba.conf entries defined correctly!
Fortunately, pg_hba.conf is pretty easy.
>> And from a technical point of view, one Postgresql system can better manage the
>> memory on a VM than two which don't know about each other.
> Probably true. Is there something with which multiple clusters running
> on the same server can communicate to do that better?
A /meta/ postmaster!!!
--
Born in Arizona, moved to Babylonia.
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: <b31d1248-7307-0b4e-38cc-2d8ff51c3b90@gmail.com>
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> <7636ea3e-fab7-1681-4e7e-464faa2d127f@gmail.com> <d22f21d-e256-15aa-9d79-68522af2edd0@evolvis.org> <b31d1248-7307-0b4e-38cc-2d8ff51c3b90@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