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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Kirill Reshke <reshkekirill(at)gmail(dot)com>
Cc: kyzevan23(at)mail(dot)ru, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19024: Error when trying to use pg_dump of new server on old server
Date: 2025-08-19 14:33:28
Message-ID: 575930.1755614008@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Kirill Reshke <reshkekirill(at)gmail(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Masahiko Sawada 2025-08-19 18:04:23 Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c
Previous Message Euler Taveira 2025-08-19 13:41:59 Re: BUG #19025: PostgreSQL log is not rotated