Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1uoNP4-0030Bs-H3
	for pgsql-bugs@arkaria.postgresql.org; Tue, 19 Aug 2025 14:33:35 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.94.2)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1uoNP3-00CX8Q-I9
	for pgsql-bugs@arkaria.postgresql.org; Tue, 19 Aug 2025 14:33:34 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1uoNP3-00CX8I-9U
	for pgsql-bugs@lists.postgresql.org; Tue, 19 Aug 2025 14:33:33 +0000
Received: from sss.pgh.pa.us ([68.162.161.243])
	by magus.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.96)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1uoNP1-000j6F-1g
	for pgsql-bugs@lists.postgresql.org;
	Tue, 19 Aug 2025 14:33:33 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 57JEXS3i575931;
	Tue, 19 Aug 2025 10:33:28 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Kirill Reshke <reshkekirill@gmail.com>
cc: kyzevan23@mail.ru, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #19024: Error when trying to use pg_dump of new server on old
 server
In-reply-to: 
 <CALdSSPjt6au6xdLuLBgF3DX4qCeHnSdMKwK3qL+G=jobK6EbQg@mail.gmail.com>
References: <19024-a7a3fa157f4437aa@postgresql.org>
 <CALdSSPh=WprPrf4mUY-oY7W=Um3GykrGOK5sN8CBQcX6BTZyUQ@mail.gmail.com>
 <CALdSSPjt6au6xdLuLBgF3DX4qCeHnSdMKwK3qL+G=jobK6EbQg@mail.gmail.com>
Comments: In-reply-to Kirill Reshke <reshkekirill@gmail.com>
	message dated "Tue, 19 Aug 2025 18:04:51 +0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <575929.1755614008.1@sss.pgh.pa.us>
Date: Tue, 19 Aug 2025 10:33:28 -0400
Message-ID: <575930.1755614008@sss.pgh.pa.us>
List-Id: <pgsql-bugs.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-bugs@lists.postgresql.org>
List-Owner: <mailto:pgsql-bugs-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-bugs>
Archived-At: 
 <https://www.postgresql.org/message-id/575930.1755614008%40sss.pgh.pa.us>
Precedence: bulk

Kirill Reshke <reshkekirill@gmail.com> writes:
> I will clarify a little here. The only way to fix this is to add new
> code to REL_17_STABLE for pg version >= 170000 and < 170003.
> Something like, "if postgresql in pg 17 with bug in
> pg_get_constraintdef, do not call pg_get_constraintdef for  contype =
> 'n', but describe it using pg_dump code"
> This is a very difficult solution to maintain in-core, so the only
> advice I can give is no actually update the minor version of the
> server.

No, we're not going to do that.  The correct answer here is "update to
a supported version of the server", namely the latest minor release.

			regards, tom lane