From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, David Christensen <david(dot)christensen(at)crunchydata(dot)com>, Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PATCHES] Post-special page storage TDE support |
Date: | 2023-11-09 02:47:56 |
Message-ID: | CAH2-WzmKZt7NxKXQBBz3BLPjRTghxLvw2CGHu+nZ2WWyxzZ3Yg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Nov 8, 2023 at 6:04 AM Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> 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.
The term that I have used in the past is "self-contained". Meaning
capable of being decoded more or less as-is, without any metadata, by
tools like pg_filedump.
Any design in this area should try to make things as easy to debug as
possible, for the obvious reason: encrypted data that somehow becomes
corrupt is bound to be a nightmare to debug. (Besides, we already
support tools like pg_filedump, so this isn't a new principle.)
--
Peter Geoghegan
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2023-11-09 03:04:19 | Re: Requiring recovery.signal or standby.signal when recovering with a backup_label |
Previous Message | Amit Kapila | 2023-11-09 02:41:53 | Re: Synchronizing slots from primary to standby |