PostgreSQL Anonymizer 3.2 changes masking roles and functions

PostgreSQL Anonymizer 3.2 adds seeded replacement functions with locale support and fixes privilege-escalation vulnerabilities. The extension hides or replaces sensitive database values for workflows such as masked exports and testing. This release also blocks masking as a superuser by default, so existing automation may need a dedicated database role before an upgrade.

Dalibo · PostgreSQL · Sep 9, 2026

Why it matters

Relevant to teams copying production-like data into development or maintaining existing masking jobs.

More context

The announcement was posted September 9 and carries a September 4 release dateline. Review the upgrade guide, replace deprecated pseudo_* calls and re-export masking rules after the schema change. Test the migration with a dedicated role on a staging database.

Keep in mind

Pseudonymization does not guarantee anonymity. Provider support and extension versions vary. The vendor’s speed claim was not independently measured; 1min has not audited the fixes.

Original read