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 1pznKx-0006Cg-Co for pgsql-general@arkaria.postgresql.org; Thu, 18 May 2023 23:47:11 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pznKw-0008GO-6x for pgsql-general@arkaria.postgresql.org; Thu, 18 May 2023 23:47:10 +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 1pznKv-0008GE-H4 for pgsql-general@lists.postgresql.org; Thu, 18 May 2023 23:47:09 +0000 Received: from tamriel.snowman.net ([70.109.60.50]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1pznKs-000ZfZ-R3 for pgsql-general@postgresql.org; Thu, 18 May 2023 23:47:08 +0000 Received: by tamriel.snowman.net (Postfix, from userid 1000) id E0FB65F7B7; Thu, 18 May 2023 19:47:00 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=snowman.net; s=dkim; t=1684453620; 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=VmNmuowT0/3BdVENOOb3m9quHVlf41Q3URitKEk4iiE=; b=o7hGEcR4sEBTrOl9xn1cb8EGOMhLmgAi18DCzYDiO2psqun9rTRsQQsppVLa4NFhUI6CHU AuKqHu5RxE6zCeqfzLFY6yUK2C/OwSyutSShuv4jx84lPc+WG6HoEmAIipdyOyOdaBk48P Nwgc2WRsrVt3jQh85ftsB6DcGQZP7hQ= Date: Thu, 18 May 2023 19:47:00 -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="jGQdy8fzHr1zdbX/" 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 --jGQdy8fzHr1zdbX/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Greetings, Really, please don't top-post on these lists. * Tony Xu (tony.xu@rubrik.com) wrote: > Regarding the multiple clusters idea, how does that work? Assume we can > store one customer's data in one cluster, is it possible to have separate > KEK for different clusters? In the proposed TDE work, yes, each cluster (which is an entier PostgreSQL system) would be able to have its own KEK. > Why not using multiple clusters then? There's a bit of overhead from each cluster and each would have their own shared buffers pool of memory and such. > Better isolation of the customers, but still on one server. Depending on the OS, multi-cluster management on a given system is easier or harder. In my view, at least, Debian systems make having multiple clusters on a given server a lot easier as they have pg_createcluster, pg_lsclusters, etc, commands and management tools. Another alternative would be to use container technology and Kubernetes or OpenShift and a PG Operator to manage all the clusters across whatever systems you're running on top of. Of course, there are trade-offs to consider between all of these different approaches. Thanks, Stephen --jGQdy8fzHr1zdbX/ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEwf6gbxKhD863zrx/7WyKOINHZFUFAmRmuPIACgkQ7WyKOINH ZFVnAw//SKqwf6lyeSkQ0PsdXUK7poBGQNSOfHVsKE9hOPib9Ri8h4qxbLnnro1/ 9zxSLLNZhPgDr9AcU8FSTgEEsNo+J3NMpB/YjbigeEVBOoQ+OIEft8IgcoF0LaJW Oa5mkUOgMTML/88o7TdEWa7O0FNl7rSf2jNyN9WWwKn4hLJCIs6YvrEccRrXv6zs pCpbkVDL5GMYG374bXmyNuh250ofagud3THV4LsxRq7op+IihW/4NteOPfm5FV9z gRtj3kOAIamermx41mS8/5ZtzqaEdcfXLprHbwrmlsXvNoioO+WzYdY6/yi2y7mF 2fNA4GKy0pvm2lOK+exr2b2bcoe83ewMXO7jG2ABkiRf+jNQW+NXw0S00fZhDkGj MZriblpWkcINLZV1WPDTCicRz+30R1ch6QL8dgNccDQICHQlJ4jljxIydDH4gw6m 4/UR9MIVt96r9YAvacM7U+AUps6PSY8mnayrzbsgXtYtiQ8LsguduJSprRhNVij5 kYU+ZKi9ZjaR1iU60IX0Zgfeqpc7tr6No0kUNISE+RAztpn6wGRMCWuDkDjLXwC0 4+8YrIkKXiPIdPb3LqXoksJihcTFplHRmvGjgyVrRlZ/tqmQrC6lS5zSMATxgtFh 5UzVnLPyACEO9mR6kvtV6NdLGfU9RFvaQnwUPkAkQpbN0RZONYs= =PsbA -----END PGP SIGNATURE----- --jGQdy8fzHr1zdbX/--