Re: BUG #19024: Error when trying to use pg_dump of new server on old server

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>

To: Kirill Reshke <reshkekirill@gmail.com>

Cc: kyzevan23@mail.ru, pgsql-bugs@lists.postgresql.org

Date: 2025-08-19T14:33:28Z

Lists: pgsql-bugs

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Fix missing "use Test::More" in Kerberos.pm.
- 71ee96e9f958 17.7 cited
pg_dump: include comments on not-null constraints on domains, too
- 6b755d8d70b2 17.6 cited

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