Re: Upgrading to v12 - Mailing list pgsql-general

From Adrian Klaver
Subject Re: Upgrading to v12
Date
Msg-id d7897b14-f85f-f454-dfd8-0fc367b0220a@aklaver.com
Whole thread Raw
In response to Re: Upgrading to v12  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On 11/12/22 22:07, Tom Lane wrote:
> Ron <ronljohnsonjr@gmail.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.

I stand corrected.

I should have read the Notes here:

https://www.postgresql.org/docs/current/app-pgdump.html

> 
>             regards, tom lane
> 
> 

-- 
Adrian Klaver
adrian.klaver@aklaver.com




pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: Upgrading to v12
Next
From: Laurenz Albe
Date:
Subject: Re: Table : Bloat grow high