From: Scott Ribe <scott_ribe@elevated-dev.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin <pgsql-admin@postgresql.org>
Cc: hemy_perry@mentor.com
Subject: Re: pg_dump from older version and pg_restore in newer
Date: Sun, 18 Jan 2015 14:42:37 -0700
Message-ID: <686190CB-0222-4E9A-9A94-68B20CCD034B@elevated-dev.com> (raw)
In-Reply-To: <6397.1421609191@sss.pgh.pa.us>
References: <CCA7F829407A9D46B8358520B195A929CE71B55C@EU-MBX-04.mgc.mentorg.com>
<3552A244-5681-4C35-A2EF-241089E54A86@elevated-dev.com>
<6397.1421609191@sss.pgh.pa.us>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
On Jan 18, 2015, at 12:26 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> In principle, ie in the absence of bugs, it should work either way.
...
> The reason for the standard recommendation to use the newer version's
> pg_dump is the possibility that your old pg_dump contains bugs that have
> been fixed in the newer version. This is a non-negligible risk when
> you're talking about a pg_dump that's several years old, as 9.1.7 is.
> If you were comparing minor releases of similar date, eg 9.1.14 versus
> 9.4.0, the risk calculation might shift the other way...
Yep. I didn't want to say it out loud in the prior post, but I don't think I have ever actually used the new dump on the old db. Then again, I'm almost never more than 1 point release behind, so my way of doing things is not generally applicable ;-)
--
Scott Ribe
scott_ribe@elevated-dev.com
http://www.elevated-dev.com/
(303) 722-0567 voice
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
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 using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: scott_ribe@elevated-dev.com, tgl@sss.pgh.pa.us, hemy_perry@mentor.com
Subject: Re: pg_dump from older version and pg_restore in newer
In-Reply-To: <686190CB-0222-4E9A-9A94-68B20CCD034B@elevated-dev.com>
* 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