MIME-Version: 1.0
References: <CACgMzfxGyCQHhE3BOrn0c8GpAd0ZMQGc80_C-qYUWZArEKqbZg@mail.gmail.com>
 <316ad242-3d52-49ca-b219-998798ed4b5c@aklaver.com>
In-Reply-To: <316ad242-3d52-49ca-b219-998798ed4b5c@aklaver.com>
From: Ashish Mukherjee <ashish.mukherjee@gmail.com>
Date: Fri, 26 Sep 2025 09:27:09 +0530
Message-ID: <CACgMzfzPEkWpGx3GpFQzZw2p-FdowsDVeGkC9A5KpOKcWsa93w@mail.gmail.com>
Subject: Re: Enquiry about Percona TDE performance issues
To: Adrian Klaver <adrian.klaver@aklaver.com>
Cc: pgsql-general@postgresql.org
Content-Type: multipart/alternative; boundary="0000000000005c2ba1063fac4804"
Archived-At: <https://www.postgresql.org/message-id/CACgMzfzPEkWpGx3GpFQzZw2p-FdowsDVeGkC9A5KpOKcWsa93w%40mail.gmail.com>
Precedence: bulk

--0000000000005c2ba1063fac4804
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

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=E2=80=AFAM Adrian Klaver <adrian.klaver@aklav=
er.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 ha=
s
> > shot up by 10x when I check explain analyze output.
>
> Did the Postgres 12 instance have the Percona TDE extension installed als=
o?
>
> How did you do the upgrade?
>
> Did you run ANALYZE on the new Postgres 17 instance?
>
>
> >
> > Regards,
> > Ashish
>
>
> --
> Adrian Klaver
> adrian.klaver@aklaver.com
>

--0000000000005c2ba1063fac4804
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Yes, PgSQL 12 also had TDE<div><br></div><div>The upgrade =
was done by taking a complete dump of the schema=C2=A0+ data from v12 insta=
nce and then restoring to v17. Used pg_dump and pg_restore respectively.</d=
iv><div><br></div><div>Yes, Vacuum analyze was also run on the new instance=
.</div></div><br><div class=3D"gmail_quote gmail_quote_container"><div dir=
=3D"ltr" class=3D"gmail_attr">On Fri, Sep 26, 2025 at 12:40=E2=80=AFAM Adri=
an Klaver &lt;<a href=3D"mailto:adrian.klaver@aklaver.com">adrian.klaver@ak=
laver.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex">On 9/25/25 04:36, Ashish Mukherjee wrote:<br>
&gt; Hello,<br>
&gt; <br>
&gt; I recently upgraded from pgsql 12 to pgsql 17. It&#39;s a Percona TDE =
<br>
&gt; enabled database. However, after the upgrade the query planning time h=
as <br>
&gt; shot up by 10x when I check explain analyze output.<br>
<br>
Did the Postgres 12 instance have the Percona TDE extension installed also?=
<br>
<br>
How did you do the upgrade?<br>
<br>
Did you run ANALYZE on the new Postgres 17 instance?<br>
<br>
<br>
&gt; <br>
&gt; Regards,<br>
&gt; Ashish<br>
<br>
<br>
-- <br>
Adrian Klaver<br>
<a href=3D"mailto:adrian.klaver@aklaver.com" target=3D"_blank">adrian.klave=
r@aklaver.com</a><br>
</blockquote></div>

--0000000000005c2ba1063fac4804--