| From: | Ashish Mukherjee <ashish(dot)mukherjee(at)gmail(dot)com> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Enquiry about Percona TDE performance issues |
| Date: | 2025-09-26 03:57:09 |
| Message-ID: | CACgMzfzPEkWpGx3GpFQzZw2p-FdowsDVeGkC9A5KpOKcWsa93w@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Yes, PgSQL 12 also had TDE
The upgrade was done by taking a complete dump of the schema + data from
v12 instance and then restoring to v17. Used pg_dump and pg_restore
respectively.
Yes, Vacuum analyze was also run on the new instance.
On Fri, Sep 26, 2025 at 12:40 AM Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
wrote:
> On 9/25/25 04:36, Ashish Mukherjee wrote:
> > Hello,
> >
> > I recently upgraded from pgsql 12 to pgsql 17. It's a Percona TDE
> > enabled database. However, after the upgrade the query planning time has
> > shot up by 10x when I check explain analyze output.
>
> Did the Postgres 12 instance have the Percona TDE extension installed also?
>
> How did you do the upgrade?
>
> Did you run ANALYZE on the new Postgres 17 instance?
>
>
> >
> > Regards,
> > Ashish
>
>
> --
> Adrian Klaver
> adrian(dot)klaver(at)aklaver(dot)com
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2025-09-26 05:25:39 | Re: Compatibility Informations |
| Previous Message | Adrian Klaver | 2025-09-25 20:21:07 | Re: Additional options for COPY from |