Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pziyU-0003qD-Lf for pgsql-general@arkaria.postgresql.org; Thu, 18 May 2023 19:07:42 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pziyT-0002sm-6v for pgsql-general@arkaria.postgresql.org; Thu, 18 May 2023 19:07:41 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pziyS-0002sc-SL for pgsql-general@lists.postgresql.org; Thu, 18 May 2023 19:07:40 +0000 Received: from evolvis.org ([217.144.135.11]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1pziyL-000aHv-Fh for pgsql-general@lists.postgresql.org; Thu, 18 May 2023 19:07:40 +0000 Received: from x61w.mirbsd.org (2001-4dd7-f4cf-0-21f-3bff-fe0d-cbb1.ipv6dyn.netcologne.de [IPv6:2001:4dd7:f4cf:0:21f:3bff:fe0d:cbb1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (Client did not present a certificate) by evolvis.org (Postfix) with ESMTPSA id 815E21002AC; Thu, 18 May 2023 19:07:32 +0000 (UTC) Received: by x61w.mirbsd.org (Postfix, from userid 1000) id 169FE613CC; Thu, 18 May 2023 21:07:32 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by x61w.mirbsd.org (Postfix) with ESMTP id 1116A60432; Thu, 18 May 2023 21:07:32 +0200 (CEST) Date: Thu, 18 May 2023 21:07:32 +0200 (CEST) From: Thorsten Glaser To: Ron cc: pgsql-general@lists.postgresql.org Subject: Re: Would PostgreSQL 16 native transparent data encryption support database level encryption? In-Reply-To: <7636ea3e-fab7-1681-4e7e-464faa2d127f@gmail.com> Message-ID: References: <7636ea3e-fab7-1681-4e7e-464faa2d127f@gmail.com> Content-Language: de-DE-1901 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Thu, 18 May 2023, Ron wrote: >> Why not using multiple clusters then? > > Yet More Firewall Rules to get approved by the Security Team.=C2=A0 And t= hen 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. > And from a technical point of view, one Postgresql system can better mana= ge 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? bye, //mirabilos --=20 15:41=E2=8E=9C Somebody write a testsuite for hello= world :-)