Re: [GENERAL] Run statements before pg_dump in same transaction? - Mailing list pgsql-general

From Alban Hertroys
Subject Re: [GENERAL] Run statements before pg_dump in same transaction?
Date
Msg-id D3AF4A98-805C-46A8-A557-6507B4FDEA41@gmail.com
Whole thread Raw
In response to Re: [GENERAL] Run statements before pg_dump in same transaction?  (John R Pierce <pierce@hogranch.com>)
List pgsql-general
> On 23 Mar 2017, at 20:23, John R Pierce <pierce@hogranch.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'sgrowing and we want to reduce risks. To that end, we'd like to anonymize the data before it leaves the
databaseserver. 
>
> 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
setsuseful for development or statistical analysis, whilst preventing people from obtaining sensitive information from
thedata set. For example, companies want to know how many facebook users are interested in buying drones, but those
companiesshould 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.



pgsql-general by date:

Previous
From: "Armand Pirvu (home)"
Date:
Subject: [GENERAL] audit function and old.column
Next
From: Adrian Klaver
Date:
Subject: Re: [GENERAL] audit function and old.column