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.
It allows updating the original data - https://postgresql-anonymizer.readthedocs.io/en/stable/stati...
> These methods will destroy the original data. Use with care.
So basically running SELECT anon.anonymize_database(); will do it.
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.