From: | Alban Hertroys <haramrae(at)gmail(dot)com> |
---|---|
To: | John R Pierce <pierce(at)hogranch(dot)com> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Run statements before pg_dump in same transaction? |
Date: | 2017-03-23 21:44:36 |
Message-ID: | D3AF4A98-805C-46A8-A557-6507B4FDEA41@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> On 23 Mar 2017, at 20:23, John R Pierce <pierce(at)hogranch(dot)com> wrote:
>
> On 3/23/2017 12:06 PM, François Beausoleil wrote:
>> For development purposes, we dump the production database to local. It's fine because the DB is small enough. The company's growing and we want to reduce risks. To that end, we'd like to anonymize the data before it leaves the database server.
>
> how about piping the /output/ of pg_dump to GPG or a similar file/stream encryption module ?
John, anonymising data is not about encrypting, but about making data anonymous. This is usually done to create data sets useful for development or statistical analysis, whilst preventing people from obtaining sensitive information from the data set. For example, companies want to know how many facebook users are interested in buying drones, but those companies should not know who exactly those people are.
ISTR that there are some tools for this purpose, but the details escape me.
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll find there is no forest.
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2017-03-23 23:38:38 | Re: audit function and old.column |
Previous Message | Armand Pirvu (home) | 2017-03-23 21:00:23 | audit function and old.column |