<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>TDE on Percona Community</title><link>https://percona.community/tags/tde/</link><description>Recent content in TDE on Percona Community</description><generator>Hugo 0.147.5</generator><language>en</language><lastBuildDate>Mon, 20 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://percona.community/tags/tde/index.xml" rel="self" type="application/rss+xml"/><item><title>TDE performance in PostgreSQL</title><link>https://percona.community/blog/2026/07/20/tde-performance-in-postgresql/</link><pubDate>Mon, 20 Jul 2026 00:00:00 +0000</pubDate><guid isPermaLink="true">https://percona.community/blog/2026/07/20/tde-performance-in-postgresql/</guid><description>&lt;p>What&amp;rsquo;s the impact of TDE on performance?
People usually quickly throw together a few graphs with basic measurements and treat that as a complete answer, but the question is a bit more complex than that.
In this blog post, I&amp;rsquo;ll try to explain it in a bit more detail: why showcasing a single graph isn&amp;rsquo;t good for anything other than marketing.&lt;/p>
&lt;p>
&lt;figure>
&lt;img sizes="100vw" srcset="https://percona.community/blog/2026/07/pg_tde_superfast_hu_d8bbf5c2f83b4aae.png 480w, https://percona.community/blog/2026/07/pg_tde_superfast_hu_5177e6d4a53024ab.png 768w, https://percona.community/blog/2026/07/pg_tde_superfast_hu_f80f6f52f50a83c5.png 1400w"
src="https://percona.community/blog/2026/07/pg_tde_superfast.png" alt="It’s SUPER FAST!" />&lt;/figure>&lt;/p>
&lt;h2 id="agenda">Agenda&lt;/h2>
&lt;p>Let me start by making something clear: this is a complex topic, and this will be a long blog post.&lt;/p></description></item><item><title>pg_tde: our fork is temporary, our commitment to open TDE is not</title><link>https://percona.community/blog/2026/07/08/pg_tde-our-fork-is-temporary-our-commitment-to-open-tde-is-not/</link><pubDate>Wed, 08 Jul 2026 00:00:00 +0000</pubDate><guid isPermaLink="true">https://percona.community/blog/2026/07/08/pg_tde-our-fork-is-temporary-our-commitment-to-open-tde-is-not/</guid><description>&lt;p>Recently we noticed a LinkedIn post promoting &lt;a href="https://github.com/commandprompt/open_pg_tde" target="_blank" rel="noopener noreferrer">open_pg_tde&lt;/a>, a fork of our &lt;a href="https://github.com/percona/pg_tde" target="_blank" rel="noopener noreferrer">pg_tde&lt;/a>, claiming to be more open.
I looked at the repository, and have to disagree with their claim.
In this blog post, I&amp;rsquo;ll explain why.&lt;/p>
&lt;p>The short version: open_pg_tde needs the exact same modified PostgreSQL that pg_tde does &amp;ndash; TDE isn&amp;rsquo;t possible without those upstream changes.
The only difference is delivery: they ship those changes as a patch file users have to apply by hand, while we provide a ready-made branch.&lt;/p></description></item></channel></rss>