public inbox for [email protected]
help / color / mirror / Atom feedFrom: Chris Travers <[email protected]>
To: [email protected]
Cc: David Christensen <[email protected]>
Subject: Re: Moving forward with TDE
Date: Sun, 17 Dec 2023 06:30:50 +0000
Message-ID: <170279465004.2631682.1886882000695050104.pgcf@coridan.postgresql.org> (raw)
In-Reply-To: <CAOxo6XJY-F3mh=epBHLSyb9befM6B0PhgxCs5KO9X3C99YAQhQ@mail.gmail.com>
References: <CAOxo6XJh95xPOpvTxuP_kiGRs8eHcaNrmy3kkzWrzWxvyVkKkQ@mail.gmail.com>
<CAOxo6XJY-F3mh=epBHLSyb9befM6B0PhgxCs5KO9X3C99YAQhQ@mail.gmail.com>
Hi,
I was re-reading the patches here and there was one thing I didn't understand.
There are provisions for a separation of data encryption keys for primary and replica I see, and these share a single WAL key.
But if I am setting up a replica from the primary, and the primary is already encrypted, then do these forceably share the same data encrypting keys? Is there a need to have (possibly in a follow-up patch) an ability to decrypt and re-encrypt in pg_basebackup (which would need access to both keys) or is this handled already and I just missed it?
Best Wishes,
Chris Travers
view thread (3+ messages)
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: Moving forward with TDE
In-Reply-To: <170279465004.2631682.1886882000695050104.pgcf@coridan.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox