# TDE is now available for PostgreSQL 18 | Percona Community

**URL:** <https://forums.percona.com/t/tde-is-now-available-for-postgresql-18-percona-community/39799>\
**Category:** Community website\
**Created:** [November 28, 2025, 12:50pm UTC](https://forums.percona.com/t/tde-is-now-available-for-postgresql-18-percona-community/39799 "2025-11-28T12:50:43Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![daniil.bazhenov](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/daniil.bazhenov/32/62_2.png) [@daniil.bazhenov](https://forums.percona.com/u/daniil.bazhenov)\
**Post date:** [November 28, 2025, 12:50pm UTC](https://forums.percona.com/t/tde-is-now-available-for-postgresql-18-percona-community/39799/1 "2025-11-28T12:50:43Z")

</div>

Back in October, before [PGConf.EU](http://pgconf.eu/), I [explained the issues impacting the prolonged wait for TDE in PostgreSQL 18](https://percona.community/blog/2025/10/15/keep-calm-tde-for-postgresql-18-is-on-its-way/). Explanations were needed as users were buzzing with anticipation, and they deserved to understand what caused the delays and what the roadmap looked like. In that blog post I have shared that due to one of the features newly added in 18.0, the [Asynchronous IO (AIO)](https://www.postgresql.org/about/featurematrix/detail/asynchronous-io-aio/), we have decided to give ourselves time until 18.1 has been released to provide a build with TDE. We wanted to ensure best quality of the solution and that takes time.

* * *
This is a companion discussion topic for the original entry at [https://percona.community/blog/2025/11/28/tde-is-now-available-for-postgresql-18](https://percona.community/blog/2025/11/28/tde-is-now-available-for-postgresql-18)