pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ron <ronljohnsonjr@gmail.com>
Cc: pgsql-general@lists.postgresql.org
Subject: Re: Upgrading to v12
Date: Sun, 13 Nov 2022 01:07:25 -0500
Message-ID: <292800.1668319645@sss.pgh.pa.us> (raw)
In-Reply-To: <5bdec7a2-bfec-b0f3-2e23-09ea7c9303cf@gmail.com>
References: <CAA_1=91Vc9a2g4wKNsHoNoMuXDpqQXNhhWq0mRyJMxUAKiEkDQ@mail.gmail.com>
	<ec6d3d2e-18f7-db89-c269-b5f28cfe0183@aklaver.com>
	<CAA_1=91AU7WaHP-_4mwPVHZVskL6gQOYJ6Tm7VooEhFvtj2_cw@mail.gmail.com>
	<CAA_1=93vKW50Ny8kyEtrM=1s8CYU1isFueAOSL+zNpH1Pzzvmg@mail.gmail.com>
	<9aa1a829-3367-74cf-1630-a91a4d67d41d@aklaver.com>
	<CAA_1=90YFtyBmg-zKZ936H6ke-CmdjjKDS-xTBEfjqpAWxSKUA@mail.gmail.com>
	<CAA_1=91E8kcce-xuXTTPJaZnX-To8dOHPe3ZBKVoyZyvXNyaFw@mail.gmail.com>
	<c6fb9011-f99d-7a2e-4a29-05f4b8cdfe25@aklaver.com>
	<CAA_1=91PLFenp7aoZYy8rm76pBz4LcCScMP7cTfUKqb5PYP+gQ@mail.gmail.com>
	<c47f3b0d-042a-ea5f-6f19-593120c4815c@aklaver.com>
	<5bdec7a2-bfec-b0f3-2e23-09ea7c9303cf@gmail.com>

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.

			regards, tom lane





view thread (31+ messages)  latest in thread

Message-ID: <292800.1668319645@sss.pgh.pa.us>
Permalink:  ../292800.1668319645@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/292800.1668319645@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: tgl@sss.pgh.pa.us, ronljohnsonjr@gmail.com
  Subject: Re: Upgrading to v12
  In-Reply-To: <292800.1668319645@sss.pgh.pa.us>
  References: <CAA_1=91Vc9a2g4wKNsHoNoMuXDpqQXNhhWq0mRyJMxUAKiEkDQ@mail.gmail.com> <ec6d3d2e-18f7-db89-c269-b5f28cfe0183@aklaver.com> <CAA_1=91AU7WaHP-_4mwPVHZVskL6gQOYJ6Tm7VooEhFvtj2_cw@mail.gmail.com> <CAA_1=93vKW50Ny8kyEtrM=1s8CYU1isFueAOSL+zNpH1Pzzvmg@mail.gmail.com> <9aa1a829-3367-74cf-1630-a91a4d67d41d@aklaver.com> <CAA_1=90YFtyBmg-zKZ936H6ke-CmdjjKDS-xTBEfjqpAWxSKUA@mail.gmail.com> <CAA_1=91E8kcce-xuXTTPJaZnX-To8dOHPe3ZBKVoyZyvXNyaFw@mail.gmail.com> <c6fb9011-f99d-7a2e-4a29-05f4b8cdfe25@aklaver.com> <CAA_1=91PLFenp7aoZYy8rm76pBz4LcCScMP7cTfUKqb5PYP+gQ@mail.gmail.com> <c47f3b0d-042a-ea5f-6f19-593120c4815c@aklaver.com> <5bdec7a2-bfec-b0f3-2e23-09ea7c9303cf@gmail.com> <292800.1668319645@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox