| From: | The Hermit Hacker <scrappy(at)hub(dot)org> |
|---|---|
| To: | Lamar Owen <lamar(dot)owen(at)wgcr(dot)org> |
| Cc: | <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Upgrade issue (again). |
| Date: | 2001-05-16 23:05:27 |
| Message-ID: | Pine.BSF.4.33.0105162000010.68237-100000@mobile.hub.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 16 May 2001, Lamar Owen wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I am loathe to even bring this up, but with two messages today about it, I am
> going to be short and sweet:
>
> We don't have a reasonable upgrade path. ASCII dump->install
> new->initdb->restore is not a reasonable upgrade. It is confusing to the
> newbie, and should be fixed. We used to have an upgrade path in pg_upgrade
> - -- but it no longer works (but it was most definitely a fine effort for its
> time, Bruce!). Furthermore, the dump/restore cycle is a pain in the neck when
> tables get larger than a few hundred megabytes. It's worse when the newer
> version won't properly restore from the old dump -- and you have to edit,
> potentially by hand, a multi-gigabyte dump to get it to restore.
Personally ... I just upgraded 13 gig worth of databases using
dump/restore, didn't have to end a single file, in less then 1.5hrs from
start to finish ... *shrug*
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-05-16 23:06:48 | Re: Re: Queries across multiple databases (was: SELECT from a table in another database). |
| Previous Message | Franck Martin | 2001-05-16 22:48:13 | RE: Configurable path to look up dynamic libraries |