PostgreSQL pseudonymization guides
Task-oriented guides built on the Brume documentation. Each one starts from a real problem, shows the full configuration and the commands, and says honestly where the limits are.
Hands-on guides
Section titled “Hands-on guides”- How to anonymize a PostgreSQL database for testing — from a production database to a pseudonymized, FK-coherent test database: complete
brume.yml, commands, expected result. - Subsetting a production database without breaking foreign keys — why naive subsets break, and how a foreign-key radius around a few seed rows keeps every constraint valid.
- Copy production data to staging safely (GDPR) — a refresh pipeline where real values never land in staging, and what the GDPR still expects from you.
Understand the law
Section titled “Understand the law”- Pseudonymization vs anonymization: what the GDPR says — Art. 4(5), Recital 26, the CNIL’s three criteria, and what it means for dev and test data.
Comparisons
Section titled “Comparisons”- Brume vs PostgreSQL Anonymizer — external CLI vs in-database extension: masking modes, keys, subsetting, determinism. And when the extension is the better pick.
- Brume vs pganonymize — two YAML-driven tools, two designs: in-place rewriting vs copy-and-transform.