Re: RPMS for 7.3 beta.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Lamar Owen <lamar(dot)owen(at)wgcr(dot)org>
Cc: "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: RPMS for 7.3 beta.
Date: 2002-09-18 03:51:32
Message-ID: 14030.1032321092@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Lamar Owen <lamar(dot)owen(at)wgcr(dot)org> writes:
>> How does pg_upgrade work?
> [ pretty good description ]

You missed a key point, which is that pg_upgrade does not even try to
cope with version-to-version system catalog changes. It assumes it can
use pg_dump to dump and reload the database schema. So there is no
hope, ever, that it will be more reliable than pg_dump. All pg_upgrade
tries to do is short-circuit the moving of the bulk data.

The bald fact of the matter is that we are still a good ways away from
the point where we might be willing to freeze the system catalogs. PG
is evolving and improving by a substantial amount with every release,
and the implication of that is that there *will* be some upgrade pain.
If you don't like that ... well ... you're welcome to keep using PG 6.1
... but I haven't got a better answer.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Oliver Elphick 2002-09-18 03:54:06 Re: RPMS for 7.3 beta.
Previous Message Oliver Elphick 2002-09-18 03:44:42 Re: RPMS for 7.3 beta.