Impact of pg_tde on database operations

This page summarizes how pg_tde interacts with core PostgreSQL operations.

Area	Affected	Notes / Actions
Backups	❌ Yes	Encrypted backups require pg_tde-aware tools. See Backup with WAL encryption.
Restore	❌ Yes	Restored data remains encrypted; pg_tde transparently handles decryption. See Restore encrypted backups.
Streaming replication	⚠️ Partial	Replicas must load the pg_tde shared library (shared_preload_libraries = ‘pg_tde’). Without it, the replica will fail on operations involving tde_heap.
Logical replication	✅ No	Not affected.
Monitoring and statistics	✅ No	Not affected, including pg_stat_monitor.
Performance	⚠️ Slight	Minor CPU overhead due to enabling encryption, most noticeable on random write workloads.