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 1pzfxl-0004qP-GA for pgsql-general@arkaria.postgresql.org; Thu, 18 May 2023 15:54:45 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pzfxk-0004QJ-Dh for pgsql-general@arkaria.postgresql.org; Thu, 18 May 2023 15:54:44 +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 1pzfxj-0004Kn-MO for pgsql-general@lists.postgresql.org; Thu, 18 May 2023 15:54:44 +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 1pzfxc-000Vrt-SG for pgsql-general@postgresql.org; Thu, 18 May 2023 15:54:42 +0000 Received: by tamriel.snowman.net (Postfix, from userid 1000) id 72C6D5F7B7; Thu, 18 May 2023 11:54:31 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=snowman.net; s=dkim; t=1684425271; 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=nWNzMXs9v1opIKpq3USG14JYxTRbMFXVu6knzmCC1A0=; b=KQBaYJ+TkxRlcP56sYTsCfGVx0k5YG258yVATWhMkZ0k16XcngE0kfsPmqcyHtg6qlURHc nl3p3XxeWGg3qfpKnG58vlB43aJtWBnG4KBKkUU58sXJsG7TBnaMNGuG+v8ZZ9vCSQXpqk XJCwABqhHlEo2MoRWvhAU3LuHj0zKo4= Date: Thu, 18 May 2023 11:54:31 -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="eDU5G0t59kc/8r82" 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 --eDU5G0t59kc/8r82 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Greetings, * Tony Xu (tony.xu@rubrik.com) wrote: > The FAQ (copied below) mentioned that native transparent data encryption > might be included in 16. Is it fair to assume that it will support database > level encryption, that is, we can use two encryption keys for two databases > in the same server, respectively? How can one verify that? The current work to include TDE in PG isn't contemplating a per-database key option. What's the use-case for that? Why do you feel that you'd need two independent keys? Also, the general idea currently is that we'll have one key provided by the user which will be a KEK and then multiple DEKs (different ones for relation data vs. temporary data vs. the WAL). If you're interested in TDE in PG, we could certainly use more folks being involved and working to push it forward. Thanks, Stephen --eDU5G0t59kc/8r82 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEwf6gbxKhD863zrx/7WyKOINHZFUFAmRmSjQACgkQ7WyKOINH ZFW2yhAApJjuPqqTsxnnJjGnPJO+jSymKjuZ+jQi39jM5lqh/kqoS7b5ZeEPXL8C xENtz5zpjH+NulhHSKyVImOVG2B0bDHzA+9OphrrUiFouCOIFiR4E9r+zsIv8yca KluTLXfJqmBhM/pyKtS/pHDjygVLzyOP+aiBothF9VZI63KkwQ/HL5UUUdWI/QwJ 0MpWWGWoUIuCKdXA1G6pF7iE09aM4N0mcO6oCKn+FVOYoF54IkPPgWoiZzetA4+D FctzKWuYHyzVsNCZgWnN6U5iNuJnn76q65N3kVw7FZWHVvqJGKNZz8lZ/GEDNnWZ 2v7g8oHSahQ+Nx60fgYJYtfF3dEior6TrEuN8oKjUy71acCSMQeHpQ0I0rvcuZ/M 5T+J3g6kMjZNJ2U6A6EiamJM2f/YR4gbsUliL5+nZRi/KAwfQNXehAIj3YC8YPms C1VdWUyJHe+xu4+4jy5mqunLTDSshdb1HcyjMruKojFNEBBHa1mmcGelkeWBogUH WiqXP/jkJh/85HdRdlbIls5w/gDym9Gqw5DlInadr9E6Bgtbm4IVSkkxrkt2EFF8 6ZAz1MVaK4+IAbvGcGhRHw2tOSFdBI17GArxuUtrrACoFZ864tHEZsU7MDNWIOoT YAEvkXd+8wF2v4RSstbSkq1aTjxcS54LqVZO4mf/K9iSwrqTcSA= =XTDD -----END PGP SIGNATURE----- --eDU5G0t59kc/8r82--