From: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-admin <pgsql-admin(at)postgresql(dot)org>, hemy_perry(at)mentor(dot)com |
Subject: | Re: pg_dump from older version and pg_restore in newer |
Date: | 2015-01-18 21:42:37 |
Message-ID: | 686190CB-0222-4E9A-9A94-68B20CCD034B@elevated-dev.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Jan 18, 2015, at 12:26 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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(at)elevated-dev(dot)com
http://www.elevated-dev.com/
(303) 722-0567 voice
From | Date | Subject | |
---|---|---|---|
Next Message | John Scalia | 2015-01-19 17:06:04 | pg_upgrade issue solved |
Previous Message | Tom Lane | 2015-01-18 19:26:31 | Re: pg_dump from older version and pg_restore in newer |