Compliance for PostgreSQL DBAs
Compliance in PostgreSQL operations is applying data protection and retention practices so the database meets legal and contractual requirements, such as India's Digital Personal Data Protection Act. It involves classifying personal data, minimising and masking it, enforcing retention and deletion, and keeping audit evidence. It follows access controls on the PostgreSQL DBA path.
Stage: Security · Part of the PostgreSQL DBA roadmap · Last reviewed 19 November 2026
What to learn in Compliance
- Classify columns that hold personal data and document where they live
- Mask or pseudonymise personal data in non-production copies
- Implement a retention job that deletes or archives rows after a stated period
- Produce audit evidence of who accessed sensitive tables
- Explain how backups and replicas affect deletion requests
Compliance interview questions
How do you handle a deletion request when the user's data also exists in backups?
Delete from live tables and replicas, document that backups age out under the retention schedule, and make sure restores re-apply pending deletions, for example by keeping a deletion log. Shorter backup retention for personal data makes this simpler.
Why should production data not be copied into development databases as it is?
Developers and test tools have weaker access controls, so personal data can leak and a breach becomes likely. Use masked or synthetic data, anonymisation scripts or subsetting, and restrict who may restore production dumps.
Where Compliance fits in the PostgreSQL DBA roadmap
Compliance belongs to the Security stage (intermediate level), which takes about 4 hours. Lock it down.
Other units in this stage
Back to the full PostgreSQL DBA roadmap