Re: Would PostgreSQL 16 native transparent data encryption support database level encryption? - Mailing list pgsql-general

From Ron
Subject Re: Would PostgreSQL 16 native transparent data encryption support database level encryption?
Date
Msg-id b31d1248-7307-0b4e-38cc-2d8ff51c3b90@gmail.com
Whole thread Raw
In response to Re: Would PostgreSQL 16 native transparent data encryption support database level encryption?  (Thorsten Glaser <tg@evolvis.org>)
List pgsql-general
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.

pgsql-general by date:

Previous
From: "Arora, Nick"
Date:
Subject: Re: Unrecognized Node Type Warning
Next
From: FOUTE K. Jaurès
Date:
Subject: PostgreSQL 13 - Logical Replication - ERROR: could not receive data from WAL stream: SSL SYSCALL error: EOF detected