Re: [Proposal] Table-level Transparent Data Encryption (TDE) and Key Management Service (KMS)
Ryan Lambert <ryan@rustprooflabs.com>
From: Ryan Lambert <ryan@rustprooflabs.com>
To: Stephen Frost <sfrost@snowman.net>
Cc: Joe Conway <mail@joeconway.com>,
Tomas Vondra <tomas.vondra@2ndquadrant.com>, Bruce Momjian <bruce@momjian.us>, Masahiko Sawada <sawada.mshk@gmail.com>, Robert Haas <robertmhaas@gmail.com>, Antonin Houska <ah@cybertec.at>, Haribabu Kommi <kommi.haribabu@gmail.com>, "Moon,
Insung" <Moon_Insung_i3@lab.ntt.co.jp>, Ibrar Ahmed <ibrar.ahmad@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2019-07-10T02:54:37Z
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 →
-
Revamp the WAL record format.
- 2c03216d8311 9.5.0 cited
If a random number were generated instead its result would need to be stored somewhere too, correct? > That might also allow things like backup software to work > on these encrypted data files for page-level backups without needing > access to the key and that'd be pretty neat. +1 Ryan