Re:Fork a distributed Postgres database with Citus
by craigkerstiens on Thursday August 10, 2017 @03:20AM
(#14977212)
Great tip on the Postgres templates, they're a very much underused feature.
Fully agreed on the data anonymization, and it's something we'll think about in the future. Prior to Citus I ran product for Heroku Postgres for a number of years and the engineering team behind our database as a service is the early team that also built Heroku Postgres so it's much of the same product we aimed to create here. Anonymization absolutely makes sense we just have to figure out the right way to deliver it.
Re:Fork a distributed Postgres database with Citus
by aquadrop on Thursday August 10, 2017 @06:05AM
(#14978148)
I think one viable way is if you provide some way to insert hooks or triggers for user to be able to amend data as they want. Maybe for some having ability to mark fields to be filled with auto generated names/addresses will be enough though.
if you use Heroku Postgres Database ( production tier ), they have a fork feature as well.
if you are running Postgres on your own and for relatively small loads, it's quite trivial to create a copy of the db using Template
https://www.postgresql.org/docs/9.2/static/manage-ag-templat...While not the responsibility of a DB vendor, it would be nice if this includes some Data anonymization/randomization option.