Alvaro Herrera <alvherre@commandprompt.com> writes:
> Bruce Momjian escribi�:
>> What cases on the past have needed the new pg_dump?
> Dependency handling IIRC in 7.3 (or was it 7.2?) was a big change for
> pg_dump, and I don't think we would have liked to backpatch the pg_dump
> changes. Also, AFAIK the sequences stuff with OWNED BY also needed the
> newer pg_dump, which is more recent (8.2?). I don't think it's as rare
> as you suggest.
Note that in straightforward cases, a dump from the older pg_dump will
serve perfectly well. However there have been cases in the past where
the dump/reload behavior of a PG version was unfixably broken for
certain corner cases --- renamed serial sequences being the latest
example. In such cases, dumping with the older pg_dump and loading into
a newer DB will not give you a correct copy of the state of your old
database, whereas dumping with the new pg_dump often does (because the
newer pg_dump knows how to exploit the feature we added to solve the
problem, such as OWNED BY).
The other usual reason for recommending this is the fear that someone's
old installation may not be up-to-date to its latest patch release, and
so its pg_dump might be missing bug fixes even for problems that *are*
soluble within its release series. The thought is that the version they
are installing probably is an up-to-date one, and so its pg_dump might
have fixes the other one doesn't.
None of this matters if you have a DB you can successfully dump and
reload in the old installation version. In that case you haven't got
any dump/reload bugs you are tripping over.
regards, tom lane
