Why Postgres Lacks Transparent Data Encryption
Postgres currently lacks Transparent Data Encryption (TDE), a feature available in other major database systems. The absence of TDE has sparked ongoing debates within the Postgres community regarding its necessity and implementation. Various companies have developed their own TDE solutions for Postgres, but none are compatible with the community release, highlighting the challenges of integrating this feature into the core system.
- ▪Postgres does not have Transparent Data Encryption, unlike Oracle, SQL Server, and MySQL.
- ▪The debate over TDE's necessity in Postgres centers around its limited protection against certain threats and existing alternatives like filesystem encryption.
- ▪Five companies have created separate TDE implementations for Postgres, but none are compatible with the community version.
2 outlets in our directory ran this story, first to last over 25 hours. All of the coverage we found sits in one bucket: centre. That one-sidedness is itself worth noticing.
- ▪ Shaun Thomas on "Why Postgres Lacks Transparent Data Encryption" — r/PostgreSQL
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Pgedge |
| Canonical URL | https://www.pgedge.com/blog/why-postgres-lacks-transparent-data-encryption |
| Publication time | Fri, 29 May 2026 02:09:51 +0000 |
| Retrieval time | 2026-05-29T02:29:40.923Z |
| Last seen | 2026-05-29T02:29:40.923Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | 6qh0dygjzCGp · 2 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
If you've ever compared database feature matrices, you may have noticed something a bit peculiar. Oracle has Transparent Data Encryption. SQL Server has it. MySQL has it. Even MariaDB has it. But Postgres, which we all consider the best database engine? Conspicuously absent.It’s not that nobody wants TDE. Compliance frameworks like PCI DSS and HIPAA practically demand encryption at rest. Cloud deployments make the “stolen disk” threat model more tangible than ever. And the question comes up constantly on mailing lists, at conferences, and in every database evaluation checklist ever assembled by a procurement department. So what gives?It’s complicated.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Pgedge.
Discussion
0 commentsMore from Pgedge
