Re: BUG #19024: Error when trying to use pg_dump of new server on old server
От | Kirill Reshke |
---|---|
Тема | Re: BUG #19024: Error when trying to use pg_dump of new server on old server |
Дата | |
Msg-id | CALdSSPjt6au6xdLuLBgF3DX4qCeHnSdMKwK3qL+G=jobK6EbQg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: BUG #19024: Error when trying to use pg_dump of new server on old server (Kirill Reshke <reshkekirill@gmail.com>) |
Ответы |
Re: BUG #19024: Error when trying to use pg_dump of new server on old server
|
Список | pgsql-bugs |
On Tue, 19 Aug 2025 at 17:54, Kirill Reshke <reshkekirill@gmail.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
В списке pgsql-bugs по дате отправления: