public inbox for [email protected]  

help / color / mirror / Atom feed

From: Ashish Mukherjee <[email protected]>
To: Adrian Klaver <[email protected]>
Cc: Merlin Moncure <[email protected]>
Cc: [email protected]
Subject: Re: Downgrade pgsql 17 to pgsql 12 question
Date: Wed, 1 Oct 2025 15:03:30 +0530
Message-ID: <CACgMzfyhhBv3CfVuUPF6VviLaLLO=O3pQCgAp6BoURwJaO0aMA@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CACgMzfxO7h+Bj4T8rjTV=trM3+Uw=jOAcUE+0Kimv4DSAVU1JA@mail.gmail.com>
	<CAHyXU0ynqbCHrw3XvofEzidHow4tx1FFGNB2FUR5-wj-EhLcNQ@mail.gmail.com>
	<CACgMzfwyMxq+qVFBMXzsMFFdBKJ5aRf_REX01KHL1mcVpRKwyA@mail.gmail.com>
	<[email protected]>

I think the conclusion is to do a more thorough testing before the upgrade
next time. Have updated our playbook for upgrades to include more thorough
testing.

On Tue, Sep 30, 2025 at 8:17 PM Adrian Klaver <[email protected]>
wrote:

> 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?
>

*I upgraded multiple non TDE databases from v12 to v17 and they are all
fine.*

>
>
> > 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]
>

view thread (9+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Downgrade pgsql 17 to pgsql 12 question
  In-Reply-To: <CACgMzfyhhBv3CfVuUPF6VviLaLLO=O3pQCgAp6BoURwJaO0aMA@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox