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 1pzhkq-0000rZ-F0 for pgsql-general@arkaria.postgresql.org; Thu, 18 May 2023 17:49:32 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pzhkp-0002DA-4B for pgsql-general@arkaria.postgresql.org; Thu, 18 May 2023 17:49:31 +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 1pzhko-0002D1-Nb for pgsql-general@lists.postgresql.org; Thu, 18 May 2023 17:49:30 +0000 Received: from mail-yb1-xb31.google.com ([2607:f8b0:4864:20::b31]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1pzhkh-000ZeX-2H for pgsql-general@lists.postgresql.org; Thu, 18 May 2023 17:49:30 +0000 Received: by mail-yb1-xb31.google.com with SMTP id 3f1490d57ef6-b9246a5f3feso3840259276.1 for ; Thu, 18 May 2023 10:49:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1684432161; x=1687024161; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:from:to:cc:subject:date:message-id :reply-to; bh=ex/Pjgt8dIBq5IT2dD/4jtTZ/deWyhAD1ySWj1m23ko=; b=MQd/q4gINU5vGjIGv4Yb/53YxfI87S6iC5rJi8UWTHRVQciUgCzoFKSqm8TqffezHl QBhKUYReE39x+QjK52TPdOu1xV52USVpHThfcUP6lbss+MaZ0NpFVQkFfEJDEsM0aw5J CnzMAVSp5sZT76h032ES/t+qCyKeCaHZ3m8abIC4QTmc+Gs+gQA6JwvarsABTaNfzP0j OpTT1R7tjdvp8hQDRhqS19yuXkgQelcvJI8SW0SXYB5C3EQiLwfrKaSK/zV4X0MPVHXI ct4V47fqtadt0lw+gZD7P4AZBinpQlFQyMtZEGkCai0SDpYMvf6q7PEZvZNkLPXCPxk+ oQSw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684432161; x=1687024161; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to; bh=ex/Pjgt8dIBq5IT2dD/4jtTZ/deWyhAD1ySWj1m23ko=; b=VA2iCdUHjHlG2j5CM4iS77GurzA3zHNTmSyNg8Og/TFd9VmmfSXIEEg9MepVdYwIP/ ahV/ABzArIV2UAaLUb+5C69BE3clIK+u9SrUArmUDrORwFbgPWW9Gy0RqiOSvZcnJXcI Z6d+Thko6ysPFngWs6mVUvLga6jUIgysVTlNRX9Cra4cb0PnHHBAzhexWHvC9bLJyV56 vxs0e01WuetZUL4M1y6Po9kd2tu3lAM8u29MVYZLwCKUwGah/wODsrRFi3L2RVCXLZvx t4om95+w13JF4ca+Dkq/N5LoWoPX+IiLh2oF3d3Lx3Cs32HtmyxQduDP32tX7EVLsMZa 9YRA== X-Gm-Message-State: AC+VfDyeY7/4CukAAbMGQ4MXiiUvMz9mMI81td+3RWUDiWC89EwjX7Ad D7cN1V4d213/WfZOmVHFchlWry/DuGA= X-Google-Smtp-Source: ACHHUZ6+3rSc+goJice7BJR9ciwQofGc3uBDrfNE7ZNDtLhTA1myV2nOjPva0scc+VyozYuMtKkNIA== X-Received: by 2002:a25:d455:0:b0:ba8:4b48:1de0 with SMTP id m82-20020a25d455000000b00ba84b481de0mr1977566ybf.47.1684432161550; Thu, 18 May 2023 10:49:21 -0700 (PDT) Received: from ?IPV6:2600:1700:bd2c:b810:1894:39f8:bd0e:1dc4? ([2600:1700:bd2c:b810:1894:39f8:bd0e:1dc4]) by smtp.googlemail.com with ESMTPSA id 63-20020a250f42000000b00b9db62abff3sm474379ybp.58.2023.05.18.10.49.21 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 18 May 2023 10:49:21 -0700 (PDT) Content-Type: multipart/alternative; boundary="------------VItlnRwhUTBp5FYuZbasqgFu" Message-ID: <08c133e0-b136-ff80-886e-b0d4f621c75c@gmail.com> Date: Thu, 18 May 2023 12:49:20 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.10.0 Subject: Re: Would PostgreSQL 16 native transparent data encryption support database level encryption? Content-Language: en-US To: pgsql-general@lists.postgresql.org References: From: Ron In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------VItlnRwhUTBp5FYuZbasqgFu Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 5/18/23 10:54, Stephen Frost wrote: > 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? I don't /feel/ that key-per-database us useful; I /know/ that key-per-database is useful, since the databases can be different projects for different companies.  Each wants it's own encryption key so that no one else can get to their at-rest data. (pg_dump files will automatically be encrypted, right?) -- Born in Arizona, moved to Babylonia. --------------VItlnRwhUTBp5FYuZbasqgFu Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit On 5/18/23 10:54, Stephen Frost wrote:
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?

I don't feel that key-per-database us useful; I know that key-per-database is useful, since the databases can be different projects for different companies.  Each wants it's own encryption key so that no one else can get to their at-rest data.

(pg_dump files will automatically be encrypted, right?)

--
Born in Arizona, moved to Babylonia.
--------------VItlnRwhUTBp5FYuZbasqgFu--