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

From: Kirill Reshke <reshkekirill(at)gmail(dot)com>
To: 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 13:04:51
Message-ID: CALdSSPjt6au6xdLuLBgF3DX4qCeHnSdMKwK3qL+G=jobK6EbQg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, 19 Aug 2025 at 17:54, Kirill Reshke <reshkekirill(at)gmail(dot)com> wrote:
>
> Hi!
>
> 6e79358 fixed server support for pg_get_constraintdef, so you should
> use pg >= 17.3 for this test to work.
> pd_dump executes queries on server, so NEW pg_dump will execute on OLD
> server. We cannot change anything in 17.0 to make this example work.
> So nothing need to be done for REL_17_STABLE?
>

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.

--
Best regards,
Kirill Reshke

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Euler Taveira 2025-08-19 13:41:59 Re: BUG #19025: PostgreSQL log is not rotated
Previous Message Kirill Reshke 2025-08-19 12:54:27 Re: BUG #19024: Error when trying to use pg_dump of new server on old server