public inbox for [email protected]  

help / color / mirror / Atom feed

From: Merlin Moncure <[email protected]>
To: Ashish Mukherjee <[email protected]>
Cc: [email protected]
Subject: Re: Downgrade pgsql 17 to pgsql 12 question
Date: Sun, 28 Sep 2025 17:40:44 -0600
Message-ID: <CAHyXU0ynqbCHrw3XvofEzidHow4tx1FFGNB2FUR5-wj-EhLcNQ@mail.gmail.com> (raw)
In-Reply-To: <CACgMzfxO7h+Bj4T8rjTV=trM3+Uw=jOAcUE+0Kimv4DSAVU1JA@mail.gmail.com>
References: <CACgMzfxO7h+Bj4T8rjTV=trM3+Uw=jOAcUE+0Kimv4DSAVU1JA@mail.gmail.com>

On Fri, Sep 26, 2025 at 8:16 AM Ashish Mukherjee <[email protected]>
wrote:

> Hello,
>
> I have a strange requirement to downgrade from pgsql 17 to pgsql 12. This
> is because we found in production certain incompatibilities between both
> versions for our database. It should have been caught in testing but was
> not.
>

Agree with others that snap downgrade is not necessarily a good choice
here.  Either way, if I were in your shoes, I'd be loading a plain text
dump, maybe with some light massaging to strip out some compatibility
issues.

Can you let us know what the hang up is?  Version upgrades these days are
usually pretty painless except for some performance issues, unless you have
some unusual situations, for example, exotic extensions.

merlin

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]
  Subject: Re: Downgrade pgsql 17 to pgsql 12 question
  In-Reply-To: <CAHyXU0ynqbCHrw3XvofEzidHow4tx1FFGNB2FUR5-wj-EhLcNQ@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