Re: Re: HOLD THE PRESSES!! ... pg_dump from v7.0.3 can't import to v7.1?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: The Hermit Hacker <scrappy(at)hub(dot)org>, Joel Burton <jburton(at)scw(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Re: HOLD THE PRESSES!! ... pg_dump from v7.0.3 can't import to v7.1?
Date: 2001-04-13 17:25:39
Message-ID: 4842.987182739@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Btw., it would really seem like a neat feature if a given pg_dump suite
> would also handle the respective previous version. Otherwise we're in a
> situation like now where we've got a shiny new pg_dump but people that
> want to upgrade are still stuck with the broken 7.0 incarnation.

No more stuck than they were if they had needed to reload from their
dump files into 7.0.

I really doubt that it's worth going out of our way to try to keep
pg_dump compatible with obsolete backends. If we had infinite manpower,
then sure, but I think the time is better spent elsewhere.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Myers 2001-04-13 17:50:31 Truncation of object names
Previous Message Tom Lane 2001-04-13 17:22:38 Re: Maybe a plpgsql bug?