MIME-Version: 1.0
References: <CAMnJ+Bet04kPY8KFxKA6tYaCGmxEhwvYoPZ1eGOHoVAJp=1rKA@mail.gmail.com>
 <f80e8077-634f-4c00-a67a-2fd0fa931cde@aklaver.com>
In-Reply-To: <f80e8077-634f-4c00-a67a-2fd0fa931cde@aklaver.com>
From: Pawel Veselov <pawel.veselov@gmail.com>
Date: Wed, 23 Apr 2025 22:02:25 +0200
Message-ID: <CAMnJ+BdUEu2vNxCEzMtOq2tYPGx2ag1Djm-nP41fPUVV35kY9g@mail.gmail.com>
Subject: Re: Dump version issues
To: Adrian Klaver <adrian.klaver@aklaver.com>
Cc: pgsql-general@lists.postgresql.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://www.postgresql.org/message-id/CAMnJ%2BBdUEu2vNxCEzMtOq2tYPGx2ag1Djm-nP41fPUVV35kY9g%40mail.gmail.com>
Precedence: bulk

On Wed, Apr 23, 2025 at 9:13=E2=80=AFPM Adrian Klaver <adrian.klaver@aklave=
r.com> wrote:

> On 4/23/25 11:46, Pawel Veselov wrote:
> > Hello.
>
> > So, how come older software (according to versions) produces dump
> > files with a greater version
> > than the newer software can understand? Is this Ubuntu package
> > maintainers messing things up?
>
> Do:
>
> man postgresql-common
>
> to see how this handled.
>
> I have found that it is best to be explicit using the --cluster option.

Thank you, I would have never guessed.

$ pg_dump -V -h x
pg_dump (PostgreSQL) 17.4 (Ubuntu 17.4-1.pgdg22.04+2)
$ pg_dump -V
pg_dump (PostgreSQL) 12.20 (Ubuntu 12.20-0ubuntu0.20.04.1)

(facepalm)

I was using the latter checking what pg_dump version was actually being use=
d.
Wasn't aware of this pg_wrapper business.

> Given a pg_dump, it would be nice if its "-V" output would say which
> version of the dump it would produce

Yeah, this wouldn't have helped a bit.