Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1r0jAP-007Qv2-3k for pgsql-hackers@arkaria.postgresql.org; Wed, 08 Nov 2023 14:04:25 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1r0jAN-003fcA-G2 for pgsql-hackers@arkaria.postgresql.org; Wed, 08 Nov 2023 14:04:23 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1r0jAM-003fbw-RH for pgsql-hackers@lists.postgresql.org; Wed, 08 Nov 2023 14:04:23 +0000 Received: from tamriel.snowman.net ([2001:470:e38f::11]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1r0jAK-005MP9-4e for pgsql-hackers@postgresql.org; Wed, 08 Nov 2023 14:04:22 +0000 Received: by tamriel.snowman.net (Postfix, from userid 1000) id 6737F5F7B7; Wed, 8 Nov 2023 09:04:13 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=snowman.net; s=dkim; t=1699452253; 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=9B7Ivt9m+V/v4CtoFe713/LdwqiCb4NGkqCPOtOTrS4=; b=iBocb5ZYtW/kn3e7+JkseUILV3xq0gL40OvVoDy1vOOZEUyF/vJUQmiT6JbuyVH3TlZJGj vKNtLWerh5a4RPionFqYMFz7BhrQHIZ9hWiNiUNIdFbd9Kc5YTRKGRnCG/6Wij6HCA3EVz Xy49s+PA8qfWt1sZ8wJQr/KEETMzzJM= Date: Wed, 8 Nov 2023 09:04:13 -0500 From: Stephen Frost To: Andres Freund Cc: David Christensen , Matthias van de Meent , Peter Geoghegan , PostgreSQL-development Subject: Re: [PATCHES] Post-special page storage TDE support Message-ID: References: <20231108002011.2c7amddaul7dhkbd@awork3.anarazel.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="B/hOK1aIJd+5J92k" Content-Disposition: inline In-Reply-To: <20231108002011.2c7amddaul7dhkbd@awork3.anarazel.de> 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 --B/hOK1aIJd+5J92k Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Greetings, * Andres Freund (andres@anarazel.de) wrote: > On 2023-05-09 17:08:26 -0500, David Christensen wrote: > > From 965309ea3517fa734c4bc89c144e2031cdf6c0c3 Mon Sep 17 00:00:00 2001 > > From: David Christensen > > Date: Tue, 9 May 2023 16:56:15 -0500 > > Subject: [PATCH v4 1/3] Add reserved_page_space to Page structure > > > > This space is reserved for extended data on the Page structure which wi= ll be ultimately used for > > encrypted data, extended checksums, and potentially other things. This= data appears at the end of > > the Page, after any `pd_special` area, and will be calculated at runtim= e based on specific > > ControlFile features. > > > > No effort is made to ensure this is backwards-compatible with existing = clusters for `pg_upgrade`, as > > we will require logical replication to move data into a cluster with > > different settings here. >=20 > The first part of the last paragraph makes it sound like pg_upgrade won't= be > supported across this commit, rather than just between different settings= =2E.. >=20 > I think as a whole this is not an insane idea. A few comments: Thanks for all the feedback! > - Why is it worth sacrificing space on every page to indicate which featu= res > were enabled? I think there'd need to be some convincing reasons for > introducing such overhead. In conversations with folks (my memory specifically is a discussion with Peter G, added to CC, and my apologies to Peter if I'm misremembering) there was a pretty strong push that a page should be able to 'stand alone' and not depend on something else (eg: pg_control, or whatever) to provide info needed be able to interpret the page. For my part, I don't have a particularly strong feeling on that, but that's what lead to this design. Getting a consensus on if that's a requirement or not would definitely be really helpful. Thanks, Stephen --B/hOK1aIJd+5J92k Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEwf6gbxKhD863zrx/7WyKOINHZFUFAmVLlVoACgkQ7WyKOINH ZFXOMw/8D0e1t5DL17/E3U3GWNwFxcByOduTR0wKbaR8qx3+N5S5B4gq71wj32qs QQeonfVt/5Fo1Nt+EWAECjVqEzeqGpogKWzMsmzN5HKV2rq2LXKysvFjMKc05mn1 RBwTLkcm42xAaFyf8ZES394YQQPQER7M0oorKLZRLeZdk9eGBQ5OMDeQMc68hWWD 5JSnuxro9N/w7kSzaB+N4/Z1DHBMKv17sH0e+21AftFMv6rWBhKmn4+clkGb5Y47 FEgD7L7mXUZk6W8kIdGAC93Ayp3zrAGmBLDuiD+qDyMcgtXJ3ILhOiAYNqyGYqDr 9DujupLZV1NEHta9Cv46EY34K//9zDsv0J27+b2pD0Fh7gQs+BSf7J5sxoH5iJAR PwrUjbnq9Xgyq5AAZc/0sElEL6lvjHEy+8lZvj0u7rGgkLTAbpXXQgutllJ5h1Pq vKfwo7XptJZVnt3ik+Lza2Yk76tZW5j6MZUiJwnpVkXWw9zsLCS+axoO9bySnwSB zCZJweFzfo++YCjaOPKMB4plriEMKTiAtDqNpPTBfNowFJO2k2ylLHIRky9fANsI T3n4pjZdL7kY27dW/Vq4XIXwxho/zFZi/JlE6Smd+xoRUiyiPopjSD5XEpNnjyqN m20s4G4xgeb4a1ED0yfbywWKrdrCJgmNLpG8iDoUswgl7hFGYaI= =V4YR -----END PGP SIGNATURE----- --B/hOK1aIJd+5J92k--