On 9/30/25 01:23, Ashish Mukherjee wrote:
Thank you all for your inputs.
Well, Percona TDE was leading to the queries being very inefficient /
slow after upgrading to pgsql 17. Explain analyze shows that query
planning time shoots up crazily. A decision was taken to go back to
How did you determine that Percona TDE was the issue vs a 5 version jump
in Postgres?
Now the consideration is to use some other encryption option for the
database which will work fine on pgsql 17. Cybertec's technology is one
route, the other is EDB. I am happy to hear experiences of folks here
with pgsql encryption options for v17 on large databases (2.5T in our case).
Personally I would verify first that you are not hitting some more
general issue with the 5 years of changes in Postgres since the last
release of 12 and current release of 17.
On Mon, Sep 29, 2025 at 5:10 AM Merlin Moncure <[email protected]
<mailto:[email protected]>> wrote:
--
Adrian Klaver
[email protected]
