MIME-Version: 1.0
References: <CACgMzfxO7h+Bj4T8rjTV=trM3+Uw=jOAcUE+0Kimv4DSAVU1JA@mail.gmail.com>
In-Reply-To: <CACgMzfxO7h+Bj4T8rjTV=trM3+Uw=jOAcUE+0Kimv4DSAVU1JA@mail.gmail.com>
From: Merlin Moncure <mmoncure@gmail.com>
Date: Sun, 28 Sep 2025 17:40:44 -0600
Message-ID: <CAHyXU0ynqbCHrw3XvofEzidHow4tx1FFGNB2FUR5-wj-EhLcNQ@mail.gmail.com>
Subject: Re: Downgrade pgsql 17 to pgsql 12 question
To: Ashish Mukherjee <ashish.mukherjee@gmail.com>
Cc: pgsql-general@postgresql.org
Content-Type: multipart/alternative; boundary="000000000000e5f839063fe50c33"
Archived-At: <https://www.postgresql.org/message-id/CAHyXU0ynqbCHrw3XvofEzidHow4tx1FFGNB2FUR5-wj-EhLcNQ%40mail.gmail.com>
Precedence: bulk

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

On Fri, Sep 26, 2025 at 8:16=E2=80=AFAM Ashish Mukherjee <ashish.mukherjee@=
gmail.com>
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

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

<div dir=3D"ltr"><div dir=3D"ltr">On Fri, Sep 26, 2025 at 8:16=E2=80=AFAM A=
shish Mukherjee &lt;<a href=3D"mailto:ashish.mukherjee@gmail.com">ashish.mu=
kherjee@gmail.com</a>&gt; wrote:</div><div class=3D"gmail_quote gmail_quote=
_container"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0=
.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"l=
tr">Hello,<div><br></div><div>I have a strange requirement to downgrade fro=
m pgsql 17 to pgsql 12. This is because we found in production certain inco=
mpatibilities=C2=A0between both versions for our database. It should have b=
een caught in testing but was not.<br></div></div></blockquote><div><br></d=
iv><div>Agree with others that snap downgrade is not necessarily a good cho=
ice here.=C2=A0 Either way, if I were in your shoes, I&#39;d be loading a p=
lain text dump, maybe with some light massaging to strip out some compatibi=
lity issues.</div><div><br></div><div>Can you let us know what the hang up =
is?=C2=A0 Version upgrades these days are usually pretty painless except fo=
r some performance issues, unless you have some unusual situations, for exa=
mple, exotic extensions.=C2=A0</div><div><br></div><div>merlin</div><div><b=
r></div></div></div>

--000000000000e5f839063fe50c33--