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 1q1BMo-0002nT-CY for pgsql-general@arkaria.postgresql.org; Mon, 22 May 2023 19:38:50 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1q1BMn-00077s-0a for pgsql-general@arkaria.postgresql.org; Mon, 22 May 2023 19:38:49 +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 1q1BMm-00077i-IJ for pgsql-general@lists.postgresql.org; Mon, 22 May 2023 19:38:48 +0000 Received: from mail-yb1-xb2f.google.com ([2607:f8b0:4864:20::b2f]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1q1BMf-001GQ3-SS for pgsql-general@lists.postgresql.org; Mon, 22 May 2023 19:38:47 +0000 Received: by mail-yb1-xb2f.google.com with SMTP id 3f1490d57ef6-ba82d82bd39so9575160276.2 for ; Mon, 22 May 2023 12:38:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1684784321; x=1687376321; 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=v74np1fRToWhhZ4gJjZh07KVuRdBTh1OEtGuuSyzUpw=; b=q3DBsbNPKwC/RecOdiUdQJr7RmlYQvs10cYDENxOagYF3gFM2+K89X99TebC61aJIm 36k7xCpitIa3a/sXdTiFvMMjLhHqt5bZ4Xzl4e1EGW6act39buvAVGl2/IMpiXv8aSnY wIoQ5ZSEgYBhwB2Z1A2U73uou0HI5oXMdNKPEFdVK0U7d2tn8CYzP92caTABoTpZ6OVf fInHF3AM/6EjkYsO6gPGC+K35ESMT9vLG68x51HFAFSZRNUuG9SCxLLDyfMZZdahu4Xq 1HhgBi7qExx0tT8yeVRbwm+bVcxrRpy4nxgmgkKNVcXpPsGqxzadWYihxyIYsPzYsOVT bmDQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684784321; x=1687376321; 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=v74np1fRToWhhZ4gJjZh07KVuRdBTh1OEtGuuSyzUpw=; b=R6629LP6meJErBzQC6NVpVTVMiJieAuHkFWCB5gbW1fwXXv5dd8U5l6gGjvOdHtkd+ ZLqAgSm3kH9/ZNmqqz9gni+VOwZ5sJP2nhYDh6DAn1J349DOB9Ytr8qsW0nn2xjsyh2h DAjWkcn1yf/j950pk7RQx6B7Ye8DEDWZcwnHfpb6EL0RYw2FddQpxfptLVybzlnD7isf NN0IwLXthjIflI5LwzVebhTHxvKFR6Zge+JkmwQcPsUFwLSCYQ/zerYaNz+BxVU/xv0i Ly6Qn6bY8nwKWdVwAgOOzV+/hsVczj9xB+Lrlg2NY32by9YqeC6sG4jjH3UijkGHc0fO LtPg== X-Gm-Message-State: AC+VfDxsV/wIK+qoj6GVoNuYyt+oX6Fpu9GukImq+ZbupCFXBdqqK7vG Kxw8GuyJnatAPt2UwJPxcWtGlDFFtRM= X-Google-Smtp-Source: ACHHUZ5NAAn0hju3+uOZDQghdmsByoykXG516qFWbncFJRBChUCZS9ug78ukw43CAr402Yg7/QzZPQ== X-Received: by 2002:a25:cb42:0:b0:ba8:7504:5535 with SMTP id b63-20020a25cb42000000b00ba875045535mr12504017ybg.23.1684784320757; Mon, 22 May 2023 12:38:40 -0700 (PDT) Received: from ?IPV6:2600:1700:bd2c:b810:6922:b189:696b:eba2? ([2600:1700:bd2c:b810:6922:b189:696b:eba2]) by smtp.googlemail.com with ESMTPSA id v13-20020a259d8d000000b00b9e9286f1e6sm1648943ybp.55.2023.05.22.12.38.40 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 22 May 2023 12:38:40 -0700 (PDT) Content-Type: multipart/alternative; boundary="------------iakwX94TNcmLgUioJSHOzEFE" Message-ID: Date: Mon, 22 May 2023 14:38:39 -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: <08c133e0-b136-ff80-886e-b0d4f621c75c@gmail.com> <1d0735cf-b5dd-1c05-d03a-9b52ee2cc5bb@gmail.com> <5d617fb4-a2de-f6a2-f0d3-8a068ac4d83f@aklaver.com> <78CFAEC1-8D31-4CF6-AAFE-AE6C34AD0F42@thebuild.com> 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. --------------iakwX94TNcmLgUioJSHOzEFE Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 5/22/23 14:22, Tony Xu wrote: > Thanks Christophe for the clarification. > > That's not quite right. A PostgreSQL cluster (in the traditional > sense, which means one PostgreSQL server handling a particular > endpoint) is isolated from any other clusters on the same machine. > > > Thanks. I think I had a misunderstanding over the "cluster" eariler. So a > PostgreSQL cluster is a PostgreSQL server that we're talking about in > general. This means per-DB KEY within a cluster/server is impossible > without splitting the whole shared storage among databases, which is > indeed a significant amount of work. "Cluster" is to Postgres as "Instance" is to SQL Server > And, to be somewhat blunt, is Rubrik prepared to pay for it?  This > engineering effort needs to be funded by someone, since engineers have > to eat.  This is not to say that any feature someone is willing to pay > for will make it into PostgreSQL, but an effort of this size, to have > any hope of reaching the point of being accepted, will need someone to > pay the salaries of the people working on it. > > I cannot speak on behalf of Rubrik - I'm just exploring PostgreSQL as a > solution for one of my team's projects thus the questions. Nothing is > finalized yet but we prefer a managed solution provided by some cloud > infra providers so the context I'm getting here will allow me to better > understand our provider's solution and their road map. RDS Postgresql would do the job just fine.  And since you can't get to the files (only access it via port 5432 and aws cli/web, there's no need for TDE. Azure is probably the same. -- Born in Arizona, moved to Babylonia. --------------iakwX94TNcmLgUioJSHOzEFE Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit On 5/22/23 14:22, Tony Xu wrote:
Thanks Christophe for the clarification. 

That's not quite right.  A PostgreSQL cluster (in the traditional sense, which means one PostgreSQL server handling a particular endpoint) is isolated from any other clusters on the same machine.  

Thanks. I think I had a misunderstanding over the "cluster" eariler. So a PostgreSQL cluster is a PostgreSQL server that we're talking about in general. This means per-DB KEY within a cluster/server is impossible without splitting the whole shared storage among databases, which is indeed a significant amount of work.

"Cluster" is to Postgres as "Instance" is to SQL Server

 
And, to be somewhat blunt, is Rubrik prepared to pay for it?  This engineering effort needs to be funded by someone, since engineers have to eat.  This is not to say that any feature someone is willing to pay for will make it into PostgreSQL, but an effort of this size, to have any hope of reaching the point of being accepted, will need someone to pay the salaries of the people working on it.
I cannot speak on behalf of Rubrik - I'm just exploring PostgreSQL as a solution for one of my team's projects thus the questions. Nothing is finalized yet but we prefer a managed solution provided by some cloud infra providers so the context I'm getting here will allow me to better understand our provider's solution and their road map.

RDS Postgresql would do the job just fine.  And since you can't get to the files (only access it via port 5432 and aws cli/web, there's no need for TDE.

Azure is probably the same.

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