Auditing UPSERTs in PostgreSQL 18: Change Tracking and Real-World Security Lessons

PostgreSQL 18 promises to track what changed by your UPSERTs, turning ad-hoc logs into auditable trails. That idea hits a security nerve after EY's 4TB data leak spotlighted the risk of untracked backups. ^[1][2]

What PostgreSQL 18 Brings

The feature gives you visibility into the exact changes an UPSERT makes, helping teams understand data impact and tighten governance around writes.

Security Lessons from the EY Leak

• The EY 4TB data leak involved exposed backups tied to SQL Server; it shows why untracked backups are a risk. ^[2]
• Auditable change trails support risk management and compliance goals in real-world deployments.

Closing thought

Auditing UPSERTs isn't a gimmick—it's practical security hygiene for 2025.

References