From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Ron <ronljohnsonjr(at)gmail(dot)com> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Upgrading to v12 |
Date: | 2022-11-13 06:07:25 |
Message-ID: | 292800.1668319645@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Ron <ronljohnsonjr(at)gmail(dot)com> writes:
> On 11/11/22 23:09, Adrian Klaver wrote:
>> 2) For your explanation above, pg_dump from 9.4(5432) to pg_restore
>> 12(5433) the issue would be ...\9.4\bin\pg_dump.exe of 9.4 and pg_restore
>> of said dump file to version 12. When moving up in version you need to use
>> the newer version of pg_dump(...\12\bin\pg_dump.exe) to dump the 9.4
>> instance and then the version 12 pg_restore to the 12 instance. Both
>> programs are backwards compatible, not forwards compatible.
> Unless there's some bug (you're running a /really/ old version of 9.4), you
> might be able to get away with using the 9.4 binary.
Yeah. The recommendation to use the later version's pg_dump for a
migration is in the nature of "this is best practice", not "this is
the only way that will work". The argument for it is that the older
pg_dump might have bugs that are fixed in the newer version. But
such bugs are rare, so usually it'll work fine to use the older one.
We do endeavor to make sure that older dump output will load into
newer versions, because in disaster-recovery scenarios an older
dump might be all you have.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Alexis Zapata | 2022-11-13 14:50:40 | RE: Table : Bloat grow high |
Previous Message | Ron | 2022-11-13 05:30:50 | Re: Upgrading to v12 |