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 1nelQm-0008Pl-LI for pgsql-hackers@arkaria.postgresql.org; Wed, 13 Apr 2022 22:25:44 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nelQl-0002kr-H1 for pgsql-hackers@arkaria.postgresql.org; Wed, 13 Apr 2022 22:25:43 +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 1nelQl-0002ki-75 for pgsql-hackers@lists.postgresql.org; Wed, 13 Apr 2022 22:25:43 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nelQe-0004M4-Gi for pgsql-hackers@lists.postgresql.org; Wed, 13 Apr 2022 22:25:42 +0000 Received: from bruce by momjian.us with local (Exim 4.94.2) (envelope-from ) id 1nelQZ-00Bsim-BT; Wed, 13 Apr 2022 18:25:31 -0400 Date: Wed, 13 Apr 2022 18:25:31 -0400 From: Bruce Momjian To: Robert Haas Cc: Antonin Houska , Stephen Frost , PostgreSQL Hackers Subject: Re: Temporary file access API Message-ID: References: <4987.1644323098@antos> <20220301143431.GT10577@tamriel.snowman.net> <27013.1646738099@antos> <3146.1649408068@antos> <2132.1649664364@antos> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Mon, Apr 11, 2022 at 04:34:18PM -0400, Robert Haas wrote: > On Mon, Apr 11, 2022 at 4:05 AM Antonin Houska wrote: > > There are't really that many kinds of files to encrypt: > > > > https://wiki.postgresql.org/wiki/Transparent_Data_Encryption#List_of_the_files_that_contain_user_data > > > > (And pg_stat/* files should be removed from the list.) > > This kind of gets into some theoretical questions. Like, do we think > that it's an information leak if people can look at how many > transactions are committing and aborting in pg_xact_status? In theory > it could be, but I know it's been argued that that's too much of a > side channel. I'm not sure I believe that, but it's arguable. > Similarly, the argument that global/pg_internal.init doesn't contain > user data relies on the theory that the only table data that will make > its way into the file is for system catalogs. I guess that's not user > data *exactly* but ... are we sure that's how we want to roll here? I don't think we want to be encrypting pg_xact/, so they can get the transaction commit rate from there. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Indecision is a decision. Inaction is an action. Mark Batterson