Horton

Re: storing an explicit nonce

Ants Aasma <ants@cybertec.at>

View thread
From: Ants Aasma <ants@cybertec.at>
To: Bruce Momjian <bruce@momjian.us>
Cc: Stephen Frost <sfrost@snowman.net>, Sasasu <i@sasa.su>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2021-10-07T18:38:45Z
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 →

  1. Rethink method for assigning OIDs to the template0 and postgres DBs.

  2. pg_upgrade: Preserve database OIDs.

  3. pg_upgrade: Preserve relfilenodes and tablespace OIDs.

  4. Fix for new Boolean node

  5. Improve error handling of HMAC computations

  6. Add macro RelationIsPermanent() to report relation permanence

  7. Enhance nbtree index tuple deletion.

On Wed, 6 Oct 2021 at 23:08, Bruce Momjian <bruce@momjian.us> wrote:

> Yes, I would prefer we don't use the LSN.  I only mentioned it since
> Ants Aasma mentioned LSN use above.
>

Is there a particular reason why you would prefer not to use LSN? I
suggested it because in my view having a variable tweak is still better
than not having it even if we deem the risks of XTS tweak reuse not
important for our use case. The comment was made under the assumption that
requiring wal_log_hints for encryption is acceptable.

-- 

Ants Aasma
Senior Database Engineerwww.cybertec-postgresql.com