From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
---|---|
To: | Sam Kidman <sam(at)fresho(dot)com> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: pg_dump 17 produces files incompatible with older server versions |
Date: | 2024-10-02 18:23:40 |
Message-ID: | 8C1019F1-2158-4404-9F12-F4505AF833E2@yesql.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> On 2 Oct 2024, at 07:23, Sam Kidman <sam(at)fresho(dot)com> wrote:
> Are there any other solutions to this issue? It could be quite
> troublesome for us as we have a few different postgres server versions
> in use in different applications but we use the same set of client
> tools for all of them.
This is per design of pg_dump, the documentation states the following:
"it is not guaranteed that pg_dump's output can be loaded into a server of
an older major version — not even if the dump was taken from a server of
that version. Loading a dump file into an older server may require manual
editing of the dump file to remove syntax not understood by the older
server."
Running the appropriate version of pg_dump for the target cluster, or applying
manual (or scripted) editing of the dump file is the option.
--
Daniel Gustafsson
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2024-10-02 18:32:39 | Re: Reading execution plan - first row time vs last row time |
Previous Message | Adrian Klaver | 2024-10-02 18:23:14 | Re: pg_dump 17 produces files incompatible with older server versions |