From: Tom Lane <tgl@sss.pgh.pa.us>
To: Kirill Reshke <reshkekirill@gmail.com>
Cc: kyzevan23@mail.ru
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #19024: Error when trying to use pg_dump of new server on old server
Date: Tue, 19 Aug 2025 10:33:28 -0400
Message-ID: <575930.1755614008@sss.pgh.pa.us> (raw)
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>
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
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: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, reshkekirill@gmail.com, 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: <575930.1755614008@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox