Static masking is a “fire and forget” approach where the original sensitive data is physically overwritten on the disk with faked or scrambled values. This process is destructive. Once the data is masked, the original values are gone forever. This should only be performed on non-production environments (like Staging or Dev) or on a backup copy of your database.<\/p>\n\n\n\n
Before applying any rules, you must explicitly enable the static masking engine at both the database and role levels. This acts as a safety switch to prevent accidental data loss.<\/p>\n\n\n
\n-- Enable the extension for the current database\nanonymizer_demo=# ALTER DATABASE anonymizer_demo SET anon.static_masking = TRUE;\nALTER DATABASE\n\n-- Grant the postgres user permission to execute static masking operations\nanonymizer_demo=# ALTER ROLE postgres SET anon.static_masking = TRUE;\nALTER ROLE\n<\/pre><\/div>\n\n\nNext, you define how the data should be transformed. We use SECURITY LABEL<\/code> to attach masking logic to specific columns. This doesn’t change the data yet; it simply tells the anon extension which functions to use during the anonymization process.<\/p>\n\n\n\n-- Replace names with realistic dummy values\nanonymizer_demo=# SECURITY LABEL FOR anon ON COLUMN customer.first_name IS 'MASKED WITH FUNCTION anon.dummy_first_name()';\nSECURITY LABEL\nanonymizer_demo=# SECURITY LABEL FOR anon ON COLUMN customer.last_name IS 'MASKED WITH FUNCTION anon.dummy_last_name()';\nSECURITY LABEL\n\n-- Generate a random date within a specific age range (1950-2000)\nanonymizer_demo=# SECURITY LABEL FOR anon ON column customer.birthdate IS 'MASKED WITH FUNCTION anon.random_date_between(''1950-01-01'', ''2000-12-31'')';\nSECURITY LABEL\n\n-- Generate syntactically correct but fake emails and company names\nanonymizer_demo=# SECURITY LABEL FOR anon ON column customer.email IS 'MASKED WITH FUNCTION anon.fake_email()';\nSECURITY LABEL\nanonymizer_demo=# SECURITY LABEL FOR anon ON column customer.company IS 'MASKED WITH FUNCTION anon.fake_company()';\nSECURITY LABEL\n<\/pre><\/div>\n\n\nThis is the final execution step. Running anonymize_database() triggers the engine to scan your rules and overwrite the table data globally. Depending on the size of your database, this may take some time as it performs UPDATE operations on the disk.<\/p>\n\n\n
\nanonymizer_demo=# SELECT anon.anonymize_database();\n anonymize_database\n--------------------\n t\n(1 row)\n<\/pre><\/div>\n\n\nThe data rules have now been applied and the data have been anonymized. You can check the result with the following query:<\/p>\n\n\n
\nanonymizer_demo=# SELECT * FROM customer;\n id | birthdate | email | company | first_name | last_name\n----+------------+----------------------+----------------+------------+------------\n 1 | 1960-11-30 | lpeters@example.net | Brown and Sons | Chyna | Mertz\n 2 | 1997-09-08 | avaughan@example.com | Rice PLC | Damien | Williamson\n(2 rows)\n<\/pre><\/div>\n\n\nYou can now turn off static masking to continue with the next demo, dynamic masking:<\/p>\n\n\n
\nanonymizer_demo=# ALTER SYSTEM SET anon.static_masking TO off;\nALTER SYSTEM\nanonymizer_demo=# ALTER ROLE postgres SET anon.static_masking TO off;\nALTER ROLE\n<\/pre><\/div>\n\n\n2. Dynamic masking<\/h3>\n\n\n\n
Dynamic masking allows you to hide sensitive information from specific users (like developers or analysts) while preserving the original data for administrators or the application itself. The masking happens in memory at the moment the query is executed.<\/p>\n\n\n\n
First, we tell the database to activate the transparent masking engine. This allows the anon extension to intercept queries from specific roles and apply masking rules before the results are returned.<\/p>\n\n\n
\nanonymizer_demo=# ALTER DATABASE anonymizer_demo SET anon.transparent_dynamic_masking = TRUE;\nALTER DATABASE\n<\/pre><\/div>\n\n\nTo see show case masking in action, we will use two types of users: a masked user who sees fake data, and an unmasked user (like the superuser) who sees the actual data stored on disk.<\/p>\n\n\n\n
In this step, we create demo_user<\/code> and “tag” them with a security label that forces the masking engine to engage whenever they log in.<\/p>\n\n\n\nanonymizer_demo=# CREATE ROLE demo_user LOGIN;\nCREATE ROLE\nanonymizer_demo=# SECURITY LABEL FOR anon ON ROLE demo_user IS 'MASKED';\nSECURITY LABEL\nanonymizer_demo=# GRANT pg_read_all_data to demo_user;\nGRANT ROLE\n\nanonymizer_demo=# SECURITY LABEL FOR anon ON ROLE demo_user IS 'MASKED';\nSECURITY LABEL\n\n-- As PostgreSQL user:\n-- Ensure the postgres user remains unmasked so we can see the 'real' data\n\nanonymizer_demo=# SECURITY LABEL FOR anon ON ROLE postgres IS NULL;\nSECURITY LABEL\n<\/pre><\/div>\n\n\nWe don’t need to redefine our masking rules (for names, emails, etc.) because the SECURITY LABEL definitions we created in the static masking section are still stored in the database schema.<\/p>\n\n\n\n
Watch what happens when we query the table as demo_user:<\/p>\n\n\n
\nanonymizer_demo=> select * from customer;\n id | birthdate | email | company | first_name | last_name\n----+------------+--------------------------+------------------+------------+-----------\n 1 | 1957-02-07 | walterkristi@example.org | Fernandez-Tucker | Emelie | Rohan\n 2 | 1950-05-15 | hannah76@example.com | Leonard Group | Jane | Durgan\n(2 rows)\n<\/pre><\/div>\n\n\nIf we run the exact same command again, the output changes:<\/p>\n\n\n
\nanonymizer_demo=> select * from customer;\n id | birthdate | email | company | first_name | last_name\n----+------------+------------------------+---------------+------------+------------\n 1 | 1963-12-26 | blairpeter@example.com | Simpson Group | Tod | Balistreri\n 2 | 1971-09-14 | steven27@example.com | Davis-Hardin | Sonny | Wintheiser\n(2 rows)\n<\/pre><\/div>\n\n\nBecause the data is being generated “on-the-fly” by the masking functions, the results are dynamic. Each request produces a fresh set of data.<\/p>\n\n\n\n
Now, let’s switch back to the postgres user. Since we removed the MASKED label from this role, the engine steps aside and shows us the actual data residing on the disk (which, in this case, is the data we masked statically in the previous step).<\/p>\n\n\n
\nanonymizer_demo=# SELECT * FROM customer;\n id | birthdate | email | company | first_name | last_name\n----+------------+----------------------+----------------+------------+------------\n 1 | 1960-11-30 | lpeters@example.net | Brown and Sons | Chyna | Mertz\n 2 | 1997-09-08 | avaughan@example.com | Rice PLC | Damien | Williamson\n(2 rows)\n<\/pre><\/div>\n\n\n3. Anonymized dump<\/h3>\n\n\n\n
An Anonymized Dump allows you to export your database into a .sql<\/code> file where the sensitive data is already replaced by fake values. This is incredibly powerful because you can create a “safe” backup that can be shared with developers or consultants without ever giving them access to your live production server.<\/p>\n\n\n\nRather than using a superuser, we create a specific role whose sole purpose is to retrieve the masked version of the data during the export process.<\/p>\n\n\n
\n-- Create a specialized user for the dump process\nanonymizer_demo=# CREATE ROLE demo_ano_dumper LOGIN PASSWORD 'secret';\nCREATE ROLE\n\n-- Force the masking engine to be active for this user session\nanonymizer_demo=# ALTER ROLE demo_ano_dumper SET anon.transparent_dynamic_masking = TRUE;\nALTER ROLE\n\n-- Apply the MASKED label to the role\nanonymizer_demo=# SECURITY LABEL FOR anon ON ROLE demo_ano_dumper IS 'MASKED';\nSECURITY LABEL\n\n-- Grant permission to read all tables\nanonymizer_demo=# GRANT pg_read_all_data TO demo_ano_dumper;\nGRANT\n<\/pre><\/div>\n\n\nNow, we use the standard pg_dump utility. Because we are logging in as demo_ano_dumper, the anon extension intercepts the data export on-the-fly. We use a few specific flags to ensure the resulting file is clean and doesn’t contain the masking logic itself:<\/p>\n\n\n
\n\/u01\/app\/postgres\/product\/18\/db_1\/bin\/pg_dump anonymizer_demo --username=demo_ano_dumper --password --no-security-labels --exclude-extension="anon" --file=anonymized_dump.sql\n<\/pre><\/div>\n\n\n--no-security-labels<\/code><\/strong>: Prevents the “MASKED” tags from being exported (the new database doesn’t need to know how the data was masked).<\/p>\n\n\n\n--exclude-extension=\"anon\"<\/code><\/strong>: Ensures the recipient doesn’t need the anon<\/code> extension installed to restore the file.<\/p>\n\n\n\nIf you open the generated anonymized_dump.sql file in a text editor, you will see that the COPY commands contain the fake data, not the original sensitive information.<\/p>\n\n\n
\n--\n-- Data for Name: customer; Type: TABLE DATA; Schema: public; Owner: postgres\n--\n\nCOPY public.customer (id, birthdate, email, company, first_name, last_name) FROM stdin;\n1 1980-12-17 cannonlauren@example.com Carr-Doyle Katharina Shanahan\n2 1998-03-27 sfox@example.net Pollard and Sons Ayla Spencer\n\\.\n<\/pre><\/div>\n\n\nV. Conclusion<\/h2>\n\n\n\n
In modern development, the goal is to work with realistic data without the real-world risk. PostgreSQL Anonymizer bridges this gap by allowing you to transform sensitive production information into safe, functional datasets.<\/p>\n\n\n\n
Now that we’ve explained how to use pg_anonymizer and covered all three methods, here is a quick guide on when to use each:<\/p>\n\n\n\n
\n- Static Masking:<\/strong> Best for “cleaning” a staging database after a production refresh.<\/li>\n\n\n\n
- Dynamic Masking:<\/strong> Best for internal users (DBAs, support staff) who need to work on the live database but shouldn’t see production data.<\/li>\n\n\n\n
- Anonymized Dump:<\/strong> Best for sharing data with external partners or creating local development environments.<\/li>\n<\/ul>\n\n\n\n
In the end, whether you choose Static, Dynamic, or Dump masking, the benefits remain the same:<\/p>\n\n\n\n
\n- Utility:<\/strong> Because the data is masked with realistic functions (like
fake_email<\/code> or dummy_first_name<\/code>), your application logic\u2014like email validation or UI layout\u2014still works perfectly.<\/li>\n\n\n\n- Compliance:<\/strong> Meet GDPR, HIPAA, and internal security requirements by default.<\/li>\n\n\n\n
- Safety:<\/strong> Developers and analysts can work on real-world bugs and features without ever seeing a customer’s actual PII (Personally Identifiable Information).<\/li>\n<\/ul>\n\n\n\n
I hope you enjoyed this guide and found these examples clear and easy to follow! My goal was to show that data privacy doesn’t have to be painful for your development workflow. Don’t forget to follow the extension latest news on the official website: https:\/\/postgresql-anonymizer.readthedocs.io\/en\/latest\/<\/a><\/p>\n\n\n\nIf you have any questions about these commands or how to implement them in your own environment, feel free to reach out \ud83d\ude42<\/p>\n","protected":false},"excerpt":{"rendered":"
Sensitive data (names, emails, phone numbers, personal identifiers\u2026) should not be freely exposed outside production. When you refresh a production database to a test or staging environment, or when analysts need access to real-looking data, anonymization becomes critical. The PostgreSQL Anonymizer extension (often called anon) is an open\u2011source extension that lets you mask, fake, shuffle, […]<\/p>\n","protected":false},"author":87,"featured_media":43221,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[83],"tags":[3885,3775,3886,77],"type_dbi":[2749],"class_list":["post-43200","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-postgresql","tag-anon","tag-anonymization","tag-pg_anonymizer","tag-postgresql","type-postgresql"],"acf":[],"yoast_head":"\n
PostgreSQL Anonymizer: Simple Data Masking for DBAs - dbi Blog<\/title>\n<meta name=\"description\" content=\"Learn how to use PostgreSQL Anonymizer for static masking, dynamic masking, and anonymized dumps. Protect your production data while keeping your data functional.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.dbi-services.com\/blog\/postgresql-anonymizer-simple-data-masking-for-dbas\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"PostgreSQL Anonymizer: Simple Data Masking for DBAs\" \/>\n<meta property=\"og:description\" content=\"Learn how to use PostgreSQL Anonymizer for static masking, dynamic masking, and anonymized dumps. Protect your production data while keeping your data functional.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/postgresql-anonymizer-simple-data-masking-for-dbas\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2026-02-27T10:08:50+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-02-27T10:15:41+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2026\/02\/Gemini_Generated_Image_gzxnaigzxnaigzxn.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1024\" \/>\n\t<meta property=\"og:image:height\" content=\"726\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Joan Frey\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Joan Frey\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-anonymizer-simple-data-masking-for-dbas\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-anonymizer-simple-data-masking-for-dbas\/\"},\"author\":{\"name\":\"Joan Frey\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c03c47649664fe73b27ce457e99f5b06\"},\"headline\":\"PostgreSQL Anonymizer: Simple Data Masking for DBAs\",\"datePublished\":\"2026-02-27T10:08:50+00:00\",\"dateModified\":\"2026-02-27T10:15:41+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-anonymizer-simple-data-masking-for-dbas\/\"},\"wordCount\":1417,\"commentCount\":0,\"image\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-anonymizer-simple-data-masking-for-dbas\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2026\/02\/Gemini_Generated_Image_gzxnaigzxnaigzxn.png\",\"keywords\":[\"anon\",\"anonymization\",\"pg_anonymizer\",\"PostgreSQL\"],\"articleSection\":[\"PostgreSQL\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/postgresql-anonymizer-simple-data-masking-for-dbas\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-anonymizer-simple-data-masking-for-dbas\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-anonymizer-simple-data-masking-for-dbas\/\",\"name\":\"PostgreSQL Anonymizer: Simple Data Masking for DBAs - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-anonymizer-simple-data-masking-for-dbas\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-anonymizer-simple-data-masking-for-dbas\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2026\/02\/Gemini_Generated_Image_gzxnaigzxnaigzxn.png\",\"datePublished\":\"2026-02-27T10:08:50+00:00\",\"dateModified\":\"2026-02-27T10:15:41+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c03c47649664fe73b27ce457e99f5b06\"},\"description\":\"Learn how to use PostgreSQL Anonymizer for static masking, dynamic masking, and anonymized dumps. Protect your production data while keeping your data functional.\",\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-anonymizer-simple-data-masking-for-dbas\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/postgresql-anonymizer-simple-data-masking-for-dbas\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-anonymizer-simple-data-masking-for-dbas\/#primaryimage\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2026\/02\/Gemini_Generated_Image_gzxnaigzxnaigzxn.png\",\"contentUrl\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2026\/02\/Gemini_Generated_Image_gzxnaigzxnaigzxn.png\",\"width\":1024,\"height\":726},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-anonymizer-simple-data-masking-for-dbas\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"PostgreSQL Anonymizer: Simple Data Masking for DBAs\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/\",\"name\":\"dbi Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c03c47649664fe73b27ce457e99f5b06\",\"name\":\"Joan Frey\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/1e650cf665b4d44dd186355827c0b049d2f95c8cbb45fd10d4e7cb255be67ecb?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/1e650cf665b4d44dd186355827c0b049d2f95c8cbb45fd10d4e7cb255be67ecb?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/1e650cf665b4d44dd186355827c0b049d2f95c8cbb45fd10d4e7cb255be67ecb?s=96&d=mm&r=g\",\"caption\":\"Joan Frey\"},\"url\":\"https:\/\/www.dbi-services.com\/blog\/author\/joanfrey\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"PostgreSQL Anonymizer: Simple Data Masking for DBAs - dbi Blog","description":"Learn how to use PostgreSQL Anonymizer for static masking, dynamic masking, and anonymized dumps. Protect your production data while keeping your data functional.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.dbi-services.com\/blog\/postgresql-anonymizer-simple-data-masking-for-dbas\/","og_locale":"en_US","og_type":"article","og_title":"PostgreSQL Anonymizer: Simple Data Masking for DBAs","og_description":"Learn how to use PostgreSQL Anonymizer for static masking, dynamic masking, and anonymized dumps. Protect your production data while keeping your data functional.","og_url":"https:\/\/www.dbi-services.com\/blog\/postgresql-anonymizer-simple-data-masking-for-dbas\/","og_site_name":"dbi Blog","article_published_time":"2026-02-27T10:08:50+00:00","article_modified_time":"2026-02-27T10:15:41+00:00","og_image":[{"width":1024,"height":726,"url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2026\/02\/Gemini_Generated_Image_gzxnaigzxnaigzxn.png","type":"image\/png"}],"author":"Joan Frey","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Joan Frey","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-anonymizer-simple-data-masking-for-dbas\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-anonymizer-simple-data-masking-for-dbas\/"},"author":{"name":"Joan Frey","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c03c47649664fe73b27ce457e99f5b06"},"headline":"PostgreSQL Anonymizer: Simple Data Masking for DBAs","datePublished":"2026-02-27T10:08:50+00:00","dateModified":"2026-02-27T10:15:41+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-anonymizer-simple-data-masking-for-dbas\/"},"wordCount":1417,"commentCount":0,"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-anonymizer-simple-data-masking-for-dbas\/#primaryimage"},"thumbnailUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2026\/02\/Gemini_Generated_Image_gzxnaigzxnaigzxn.png","keywords":["anon","anonymization","pg_anonymizer","PostgreSQL"],"articleSection":["PostgreSQL"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/postgresql-anonymizer-simple-data-masking-for-dbas\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-anonymizer-simple-data-masking-for-dbas\/","url":"https:\/\/www.dbi-services.com\/blog\/postgresql-anonymizer-simple-data-masking-for-dbas\/","name":"PostgreSQL Anonymizer: Simple Data Masking for DBAs - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-anonymizer-simple-data-masking-for-dbas\/#primaryimage"},"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-anonymizer-simple-data-masking-for-dbas\/#primaryimage"},"thumbnailUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2026\/02\/Gemini_Generated_Image_gzxnaigzxnaigzxn.png","datePublished":"2026-02-27T10:08:50+00:00","dateModified":"2026-02-27T10:15:41+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c03c47649664fe73b27ce457e99f5b06"},"description":"Learn how to use PostgreSQL Anonymizer for static masking, dynamic masking, and anonymized dumps. Protect your production data while keeping your data functional.","breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-anonymizer-simple-data-masking-for-dbas\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/postgresql-anonymizer-simple-data-masking-for-dbas\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-anonymizer-simple-data-masking-for-dbas\/#primaryimage","url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2026\/02\/Gemini_Generated_Image_gzxnaigzxnaigzxn.png","contentUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2026\/02\/Gemini_Generated_Image_gzxnaigzxnaigzxn.png","width":1024,"height":726},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-anonymizer-simple-data-masking-for-dbas\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"PostgreSQL Anonymizer: Simple Data Masking for DBAs"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c03c47649664fe73b27ce457e99f5b06","name":"Joan Frey","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/1e650cf665b4d44dd186355827c0b049d2f95c8cbb45fd10d4e7cb255be67ecb?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/1e650cf665b4d44dd186355827c0b049d2f95c8cbb45fd10d4e7cb255be67ecb?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/1e650cf665b4d44dd186355827c0b049d2f95c8cbb45fd10d4e7cb255be67ecb?s=96&d=mm&r=g","caption":"Joan Frey"},"url":"https:\/\/www.dbi-services.com\/blog\/author\/joanfrey\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/43200","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/87"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=43200"}],"version-history":[{"count":25,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/43200\/revisions"}],"predecessor-version":[{"id":43250,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/43200\/revisions\/43250"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media\/43221"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=43200"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=43200"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=43200"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=43200"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}