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 1pzmUz-00040F-P4 for pgsql-general@arkaria.postgresql.org; Thu, 18 May 2023 22:53:29 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pzmUy-0002KJ-NJ for pgsql-general@arkaria.postgresql.org; Thu, 18 May 2023 22:53:28 +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 1pzmUy-0002KA-1a for pgsql-general@lists.postgresql.org; Thu, 18 May 2023 22:53:28 +0000 Received: from tamriel.snowman.net ([2001:470:e38f::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 1pzmUu-000cEl-Ei for pgsql-general@postgresql.org; Thu, 18 May 2023 22:53:27 +0000 Received: by tamriel.snowman.net (Postfix, from userid 1000) id E77A85F7B7; Thu, 18 May 2023 18:53:18 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=snowman.net; s=dkim; t=1684450398; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=RNJ6mEo1223B464bVqPJNuZvnJAt6rzFzXgVjfco8eg=; b=vtyQ5u9A6FLKTnLXrBCejxZQEpCaVy1BqIuJys35HcFR/oytAh8QKrFBOexOZBKwjJKS0V kpHiiAfehKcw90r+czSCejpOnmG13Qdhdu5JHZmoamVtsvsxeYIDkuJaSBX5GxAcxyiEsA G2b2GbWyAaQHDRFZW+DboiyuEsnJr9A= Date: Thu, 18 May 2023 18:53:18 -0400 From: Stephen Frost To: Tony Xu Cc: pgsql-general@postgresql.org Subject: Re: Would PostgreSQL 16 native transparent data encryption support database level encryption? Message-ID: References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="bAufJ2zb0Fvzg3Sj" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/2.1.4 (2021-12-11) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --bAufJ2zb0Fvzg3Sj Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Greetings, Please don't top-post on these lists. * Tony Xu (tony.xu@rubrik.com) wrote: > Our use-case is for a multi-tenancy scenario - we are considering using > different databases to store different customer's data, however, for > cost-efficiency, we want to host them in the same server (to reduce the > CPU/mem idle time and to reduce the server management efforts). Now there > is a compliance related feature that we need to let our customer control > the KEK for their databases so they can rotate their KEKs independently, so > we cannot use one KEK for the whole PG server. Conceptually, different > databases are independent of each other, it also makes sense to allow them > to have completely independent encryption facilities? This really isn't currently in the plans and while it might be something added later, as pointed out farther down on this thread, it wouldn't be possible for the shared catalogs or the WAL to have separate keys for those things which are relevant to a database, so it's not like each tenant would actually have control over the key for "all" of their data (consider that roles are stored in a shared PG catalog and then shared among databases...). To meet this compliance requirement, you'd certainly be much more able to blanket claim that everything is independent by having a separate PG instance for each client. This would also allow rather useful things like being able to do a file-based restore on a per-client basis in the event something happens, rather than having to roll back an entire cluster to some point in time just because one client did something bad.. You'd also be able to scale the number of systems supporting a given client independently. Thanks, Stephen --bAufJ2zb0Fvzg3Sj Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEwf6gbxKhD863zrx/7WyKOINHZFUFAmRmrFwACgkQ7WyKOINH ZFVqZA//R3GxHlZouX0sd6qAPgWqHB/HRwZGsJ8+NsUcDyKkuMdAFzfL9gyqdX/R BaXHC+D5z7nFVxUqbEpg4Ouvp/fVArhXvqw99ufYMumhCCuRepPWZzUYyiuVdj3b zSHom/Knfb8WbdQeiDY83sISJmsj+z5/ShGZsZfT9Z1U1MnbUroH/I88C3fASRCL t6Ct9ClMTU7DNy59M5Xp05+3X5MroiHw4Yc4+lEWl+AUTFGWdjBNjL6sYzCZgMRs akpshTz9gioG51vVDKWvTAav9Gr9dDlGYZFlFMwpz+1IYOXapa+UNUsRnStM2bgr JinZRGysRjJuYIRl7fKu8lU6MjplFA8awQFLs/LRDLzOSYJpP+boWjH/V6vWdDrz t9caKXJOV33GzrCHQ9X775hRw24Qx5wUaMdS/Ro7qIt9dqYt3s3Z93s/mddsWYNK uVgpSVeGLE5bHgNAHHrddB7aK2pFgRxDy4v21MlQbfkGNFmsaZGxOg1n2a55ZszQ 6pl3icdBewuLpDM4GcWrSExiglzDA0pT3SCHl4yFC/3EBfPJ1xo/oPRM0jSHkqKj v5s89eYsNgpjLUqvFhc0lUjYd12b0m/jLJx4ZbZL4u1gYlY06vyB5sAq1kqJr+1s FZAB33OSeGSDuSxizrhYWGx8mi9wfXeyg895jF8QpSwKRdxGZ9U= =jsgx -----END PGP SIGNATURE----- --bAufJ2zb0Fvzg3Sj--