From: | Pawel Veselov <pawel(dot)veselov(at)gmail(dot)com> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Dump version issues |
Date: | 2025-04-23 20:02:25 |
Message-ID: | CAMnJ+BdUEu2vNxCEzMtOq2tYPGx2ag1Djm-nP41fPUVV35kY9g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Apr 23, 2025 at 9:13 PM Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)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 used.
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.
From | Date | Subject | |
---|---|---|---|
Next Message | Igor Korot | 2025-04-23 20:15:08 | Re: Another documentation issue |
Previous Message | Tom Lane | 2025-04-23 19:23:20 | Re: segmentation fault |