On 7/9/19 6:07 AM, Peter Eisentraut wrote: > 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.
While it would be ideal to have separate WAL, and even separate shared buffer pools, per tablespace, I think that is too much complexity for the first implementation and we could have a single separate key for all WAL for now. The main thing I don't think we want is e.g. a 50TB database with everything encrypted with a single key -- for the reasons previously stated. -- Crunchy Data - http://crunchydata.com PostgreSQL Support for Secure Enterprises Consulting, Training, & Open Source Development
signature.asc
Description: OpenPGP digital signature
