On Tue, Feb 1, 2022 at 07:45:06AM +0100, Antonin Houska wrote: > > With pg_upgrade modified to preserve the relfilenode, tablespace oid, and > > database oid, we are now closer to implementing cluster file encryption > > using XTS. I think we have a few steps left: > > > > 1. modify temporary file I/O to use a more centralized API > > 2. modify the existing cluster file encryption patch to use XTS with a > > IV that uses more than the LSN > > 3. add XTS regression test code like CTR > > 4. create WAL encryption code using CTR > > > > If we can do #1 in PG 15 I think I can have #2 ready for PG 16 in July. > > The feature wiki page is: > > > > https://wiki.postgresql.org/wiki/Transparent_Data_Encryption > > > > Do people want to advance this feature forward? > > I confirm that we (Cybertec) do and that we're ready to spend more time on the > community implementation.
Well, I sent an email a week ago asking if people want to advance this feature forward, and so far you are the only person to reply, which I think means there isn't enough interest in this feature to advance it. -- Bruce Momjian <br...@momjian.us> https://momjian.us EDB https://enterprisedb.com If only the physical world exists, free will is an illusion.
