pg_anon caught 1 of my 8 PII columns. My schema isn't in English.
In a DEV Community post, developer Efraín Garay describes using pg_anon, a PostgreSQL anonymization tool, and finding that it caught only one of eight PII columns in their database. Garay notes that their schema is not in English, which they believe contributed to the tool's failure to identify the other seven columns. The post's title and opening line directly state: "pg_anon caught 1 of my 8 PII columns. My schema isn't in English." The full source text provided is largely CSS styling for a retro-themed DEV Community article, with no additional technical details, code examples, or configuration specifics. The only substantive content is the title and the opening sentence, which together convey the developer's experience and their hypothesis about the cause. No further information is given about the exact nature of the PII columns, the database schema language, or any steps taken to address the issue. The post appears to be part of a themed challenge (the CSS includes "THE 418 CHALLENGE"), but that is unrelated to the content. The developer's observation highlights a potential limitation of pg_anon's default PII detection when schemas use non-English column names, but the source does not provide evidence of how pg_anon's detection works or whether configuration options exist to improve detection.
Highlights that pg_anon's PII detection may miss columns in non-English schemas, affecting anonymization accuracy.