From: Tom Lane <tgl@sss.pgh.pa.us>
To: Adrian Klaver <adrian.klaver@aklaver.com>
cc: Ashish Mukherjee <ashish.mukherjee@gmail.com>,
        pgsql-general@postgresql.org
Subject: Re: Downgrade pgsql 17 to pgsql 12 question
In-reply-to: <d061e898-9a81-411b-9ecf-fb928321caff@aklaver.com>
References: <CACgMzfxO7h+Bj4T8rjTV=trM3+Uw=jOAcUE+0Kimv4DSAVU1JA@mail.gmail.com> <d061e898-9a81-411b-9ecf-fb928321caff@aklaver.com>
Comments: In-reply-to Adrian Klaver <adrian.klaver@aklaver.com>
	message dated "Fri, 26 Sep 2025 08:10:03 -0700"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <4063194.1758899637.1@sss.pgh.pa.us>
Content-Transfer-Encoding: 8bit
Date: Fri, 26 Sep 2025 11:13:57 -0400
Message-ID: <4063195.1758899637@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/4063195.1758899637%40sss.pgh.pa.us>
Precedence: bulk

Adrian Klaver <adrian.klaver@aklaver.com> writes:
> On 9/26/25 05:18, Ashish Mukherjee wrote:
>> 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.

> What are the incompatibilities?
> Might be easier to deal with those then doing the below.

Yeah ... sitting on a PG release that's already a year beyond EOL
is not a sustainable practice.  You should consult the last several
release notes for v13 and reflect on the likelihood that most of those
bugs also exist in v12.

			regards, tom lane