Re: storing an explicit nonce
Bruce Momjian <bruce@momjian.us>
From: Bruce Momjian <bruce@momjian.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Stephen Frost <sfrost@snowman.net>, Andres Freund <andres@anarazel.de>, Alvaro Herrera <alvherre@alvh.no-ip.org>, Masahiko Sawada <sawada.mshk@gmail.com>, Tom Kincaid <tomjohnkincaid@gmail.com>, Amit Kapila <amit.kapila16@gmail.com>, Thomas Munro <thomas.munro@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>, Masahiko Sawada <masahiko.sawada@2ndquadrant.com>
Date: 2021-06-25T21:22:04Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Rethink method for assigning OIDs to the template0 and postgres DBs.
- 2cb1272445d2 15.0 landed
-
pg_upgrade: Preserve database OIDs.
- aa01051418f1 15.0 landed
-
pg_upgrade: Preserve relfilenodes and tablespace OIDs.
- 9a974cbcba00 15.0 landed
-
Fix for new Boolean node
- cf925936ecc0 15.0 cited
-
Improve error handling of HMAC computations
- 5513dc6a304d 15.0 cited
-
Add macro RelationIsPermanent() to report relation permanence
- 95d77149c535 14.0 landed
-
Enhance nbtree index tuple deletion.
- d168b666823b 14.0 cited
Attachments
- cfe-01-doc_over_master.diff.gz (application/gzip) patch
- cfe-02-internaldoc_over_cfe-01-doc.diff.gz (application/gzip) patch
- cfe-03-scripts_over_cfe-02-internaldoc.diff.gz (application/gzip) patch
- cfe-04-common_over_cfe-03-scripts.diff.gz (application/gzip) patch
- cfe-05-crypto_over_cfe-04-common.diff.gz (application/gzip) patch
- cfe-06-backend_over_cfe-05-crypto.diff.gz (application/gzip) patch
- cfe-07-bin_over_cfe-06-backend.diff.gz (application/gzip) patch
- cfe-08-pg_alterckey_over_cfe-07-bin.diff.gz (application/gzip) patch
- cfe-09-test_over_cfe-08-pg_alterckey.diff.gz (application/gzip) patch
- cfe-10-hint_over_cfe-09-test.diff.gz (application/gzip) patch
- cfe-11-gist_over_cfe-10-hint.diff (text/x-diff)
On Wed, May 26, 2021 at 05:02:01PM -0400, Bruce Momjian wrote: > For these reasons, if we decide to go in the direction of using a > non-LSN nonce, I no longer plan to continue working on this feature. I > would rather work on things that have a more positive impact. Maybe a > non-LSN nonce is a better long-term plan, but there are too many > unknowns and complexity for me to feel comfortable with it. As stated above, I have no plans to continue working on this feature. I am attaching my final patches here in case anyone wants to make use of them; it passes check-world and all my private tests. I have removed my patches from the feature wiki page: https://wiki.postgresql.org/wiki/Transparent_Data_Encryption and replaced it with a link to this email. -- Bruce Momjian <bruce@momjian.us> https://momjian.us EDB https://enterprisedb.com If only the physical world exists, free will is an illusion.