Just be careful that you don't anonymize your production data.

The principle of the software seems to be that the original data is never altered. It is a postgres extension that "masks" the data for certain postgres users. You can always connect as the root user and see everything when you need to.

▲

heeton a year ago | parent [-]

It allows updating the original data - https://postgresql-anonymizer.readthedocs.io/en/stable/stati...

> These methods will destroy the original data. Use with care.

▲

sgt a year ago | parent [-]

So basically running SELECT anon.anonymize_database(); will do it.

	▲	daamien a year ago \| parent [-]
		Both approach are possible * Static Masking will destroy the authentic data once for all * Dynamic Masking will only alter the data the "masked users". Regular users will continue to view the real data. Both techniques have their own advantage depending on your context.

▲

go_prodev a year ago | parent | prev | next [-]

With great power comes great responsibility.

▲

antman a year ago | parent | prev [-]

Masking is for view for specific users