3 ms·
You'd need some sort of encryption of the raw data storage, and that would also prevent backing up any indexes. And yes, you'd expose some amount of informatio
by JoshTriplett 10y ago
You'd need some sort of encryption of the raw data storage, and that would also prevent backing up any indexes. And yes, you'd expose some amount of information, such as row activity. Seems plausible, though, depending on your threat model.
- anarazel 10y agoIf I were to do that I'd use logical decoding (https://www.postgresql.org/docs/current/static/logicaldecoding.html https://www.postgresql.org/docs/current/static/logicaldecodi...) and just write a custom apply mechanism. I think you'll, in any case, end up exposing a lot of information. INSERT/UPDATE/DELETE are going to be discernible, and you'd have to be very careful about compression not exposing things. The backup wouldn't actually be particularly useful though. So I'm not really sure what the use-case here is.