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 1pziHi-00022o-OS for pgsql-general@arkaria.postgresql.org; Thu, 18 May 2023 18:23:30 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pziHh-00052R-Ma for pgsql-general@arkaria.postgresql.org; Thu, 18 May 2023 18:23:29 +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 1pziHh-00052H-Bn for pgsql-general@lists.postgresql.org; Thu, 18 May 2023 18:23:29 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1pziHe-000X4H-UY for pgsql-general@postgresql.org; Thu, 18 May 2023 18:23:28 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 34IINHuh3867048; Thu, 18 May 2023 14:23:17 -0400 From: Tom Lane To: Thorsten Glaser cc: Tony Xu , pgsql-general@postgresql.org Subject: Re: Would PostgreSQL 16 native transparent data encryption support database level encryption? In-reply-to: References: Comments: In-reply-to Thorsten Glaser message dated "Thu, 18 May 2023 20:02:35 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3867046.1684434197.1@sss.pgh.pa.us> Date: Thu, 18 May 2023 14:23:17 -0400 Message-ID: <3867047.1684434197@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Thorsten Glaser writes: > 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? Yeah. The problem with key-per-database is what are you going to do with the shared catalogs? It's a lot simpler, and probably better performing, to use one key per cluster. regards, tom lane