From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Dave Page <dpage(at)pgadmin(dot)org>, Tony Caduto <tony_caduto(at)amsoftwaredesign(dot)com>, paul rivers <rivers(dot)paul(at)gmail(dot)com>, Postgres General List <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Pains in upgrading to 8.3 |
Date: | 2008-02-18 21:35:11 |
Message-ID: | 20080218213511.GE11594@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Bruce Momjian escribió:
> Magnus Hagander wrote:
> > For the case of upgrading, it wouldn't work. But there are certainly
> > other cases where it would help. Say from your central pgadmin console
> > administering 10 servers from 3 different major release trees :-(
What's wrong with providing statically-linked pg_dump-8.2, pg_dump-8.3
and so on, and asking the user which one to use (depending on the target
server version)?
> Using the new pg_dump for dumping older versions during an ugprade is
> just inconvenient and something we should not need to do. At the worst
> we should have a way for us to upgrade the older version of pg_dump with
> whatever functionality we need and just tell people to be running the
> most recent minor release before upgrading.
>
> 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.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Stephan Szabo | 2008-02-18 21:37:08 | Re: [HACKERS] deadlock with truncate and foreing keys |
Previous Message | Tom Lane | 2008-02-18 21:11:20 | Re: Initdb failed in PostgreSQL 7.3.21 |