Re: [Proposal] Table-level Transparent Data Encryption (TDE) and Key Management Service (KMS)
Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Joe Conway <mail@joeconway.com>, Stephen Frost <sfrost@snowman.net>,
Bruce Momjian <bruce@momjian.us>
Cc: Masahiko Sawada <sawada.mshk@gmail.com>,
Tomas Vondra <tomas.vondra@2ndquadrant.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-09T10:07:05Z
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
On 2019-07-08 18:09, Joe Conway wrote: > In my mind, and in practice to a > large extent, a postgres tablespace == a unique mount point. But a critical difference is that in file systems, a separate mount point has its own journal. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services