Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.600.62\))
Subject: Re: pg_dump 17 produces files incompatible with older server versions
From: Daniel Gustafsson <daniel@yesql.se>
In-Reply-To: <CA+FDo=vj+MPhROnDF1b6R=dPrgXeLGUaFbHu=YnHEz7LocSu4A@mail.gmail.com>
Date: Wed, 2 Oct 2024 20:23:40 +0200
Cc: pgsql-general@lists.postgresql.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <8C1019F1-2158-4404-9F12-F4505AF833E2@yesql.se>
References: <CA+FDo=vj+MPhROnDF1b6R=dPrgXeLGUaFbHu=YnHEz7LocSu4A@mail.gmail.com>
To: Sam Kidman <sam@fresho.com>
Archived-At: <https://www.postgresql.org/message-id/8C1019F1-2158-4404-9F12-F4505AF833E2%40yesql.se>
Precedence: bulk

> On 2 Oct 2024, at 07:23, Sam Kidman <sam@fresho.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 =E2=80=94 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