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 1pzhxe-0001Mc-9d for pgsql-general@arkaria.postgresql.org; Thu, 18 May 2023 18:02:46 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pzhxd-0003Gm-2R for pgsql-general@arkaria.postgresql.org; Thu, 18 May 2023 18:02:45 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pzhxc-0003FT-No for pgsql-general@lists.postgresql.org; Thu, 18 May 2023 18:02:44 +0000 Received: from evolvis.org ([217.144.135.11]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1pzhxW-000Wu0-TN for pgsql-general@postgresql.org; Thu, 18 May 2023 18:02:43 +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 2E200100029; Thu, 18 May 2023 18:02:36 +0000 (UTC) Received: by x61w.mirbsd.org (Postfix, from userid 1000) id D2D13613CC; Thu, 18 May 2023 20:02:35 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by x61w.mirbsd.org (Postfix) with ESMTP id CDA0860432; Thu, 18 May 2023 20:02:35 +0200 (CEST) Date: Thu, 18 May 2023 20:02:35 +0200 (CEST) From: Thorsten Glaser To: Tony Xu cc: pgsql-general@postgresql.org Subject: Re: Would PostgreSQL 16 native transparent data encryption support database level encryption? In-Reply-To: Message-ID: References: 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, 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 --=20 15:41=E2=8E=9C Somebody write a testsuite for hello= world :-)