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 1pzkt1-0008Q4-9c for pgsql-general@arkaria.postgresql.org; Thu, 18 May 2023 21:10: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 1pzksz-0003lM-6G for pgsql-general@arkaria.postgresql.org; Thu, 18 May 2023 21:10:09 +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 1pzksy-0003lC-Rm for pgsql-general@lists.postgresql.org; Thu, 18 May 2023 21:10:08 +0000 Received: from mail-yb1-xb2e.google.com ([2607:f8b0:4864:20::b2e]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1pzksu-000bKf-N4 for pgsql-general@lists.postgresql.org; Thu, 18 May 2023 21:10:08 +0000 Received: by mail-yb1-xb2e.google.com with SMTP id 3f1490d57ef6-ba81deea9c2so2273381276.2 for ; Thu, 18 May 2023 14:10:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1684444204; x=1687036204; h=content-transfer-encoding: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=oU9/6H834z0mDQcJKaVsQO5mwRFCvOWBryDB9Dz7qj0=; b=GQFJHOKkLPB6QQuDMWRGosvNO+BQoqM5I6x8fKVsE7pPlZs1WQu9L8YqA23M14A862 V4BIAVE0HLdXNk5BIzMRKi2eK1RUlXJ4vmoa3iKoe4+r3IKmCZwDU8a9IW76OCd4qwmU 6Qhp2O4q3F9aKzaMYSAiuR5wnmG72PbzcOx1BGWNf4pE0KSem5WyB/sjjLAOzjbE0G72 n21qubWtn4vZmLxqYnOvRwFK6FtbVN4eE8jjo+bMetyZqvBAkfIoDlXxeB16o5gFdqIv eC6IYBVxoe4pDxbhGp9Y9TfUZVE7NDxHzo309Bh43uLnMal5jmAp0s3Lm0iZjQqvaXpc lZMA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684444204; x=1687036204; h=content-transfer-encoding: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=oU9/6H834z0mDQcJKaVsQO5mwRFCvOWBryDB9Dz7qj0=; b=LOT7PERdDt2iB9ymK3W9KRGX5cynZ0PO/kaZ3GSuBVZBbU6eP7b0RSCGe+TUN6TgfF IRk3ETjl6JHWa1tjFH5zfauWZSmAvM7Dvy+v5kZAA5qcPodUANsC6aQx10KER4hcqn+I jPH097E505v/lW66U3AG4qBiknSCfs+HLdl5Yf8QHa5uI4nHSxxeZeVryCdMj2nMOvzQ YSm5GLPXJBzbVsCbptUQLMy4vHBI8Mkm9dxPjw4NtAX6L5lqrWB8WPVR695VnwD+vj2Z 9pey3gTbRmVatt6TVGCZmVWbFJES+6q4qkQ1AOgavrPUMGaIH/rLxgWwMwDEecKa3033 W1tg== X-Gm-Message-State: AC+VfDyn0oecEW2k+LxnfU9qYcEggDuZYpjnxEuHVxbJPuNWvtweD3X8 rHUvIJ6rBmkX37StAflv3z4dMz6MUOg= X-Google-Smtp-Source: ACHHUZ4Ez59KweUXlcYcr4/KTA6rGrynNCGPARNnHJ5JY2DMRqaFj+UpATjRyUVIYiA/LJivKDtpoA== X-Received: by 2002:a0d:ddd5:0:b0:561:9051:d2d3 with SMTP id g204-20020a0dddd5000000b005619051d2d3mr2617978ywe.11.1684444203580; Thu, 18 May 2023 14:10:03 -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 y8-20020a817d08000000b00545a08184fdsm657978ywc.141.2023.05.18.14.10.03 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 18 May 2023 14:10:03 -0700 (PDT) Message-ID: <5038f5c7-35f6-0dc6-129e-341dd6909ea1@gmail.com> Date: Thu, 18 May 2023 16:10:02 -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> From: Ron In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 5/18/23 15:56, Bruce Momjian wrote: > On Thu, May 18, 2023 at 01:56:48PM -0500, Ron wrote: >> We need to keep costs down, too. >> >> Oracle (I think) does it at the DB level, and so does SQL Server.  Upper >> Management hears us say "sorry, no can do" and wonders what bunch of amateurs >> are developing PostgreSQL. > I have found it is hard to protect against the judgment of the ignorant, > so I usually don't bother. It's perfectly valid to ask "why can't they do X when our previous vendor could?" I, of course, know that it's because WAL records are global.  "They" then quite reasonably ask why the developers haven't fixed that, yet.  The answer (I think) is that "global WAL"is deeply embedded in the product, and would require a major rewrite; adding new features is a higher priority. -- Born in Arizona, moved to Babylonia.