From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Lamar Owen <lamar(dot)owen(at)wgcr(dot)org> |
Cc: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] PG_UPGRADE status? |
Date: | 1999-09-08 21:43:03 |
Message-ID: | 199909082143.RAA25843@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Bruce Momjian wrote:
> >Lamar Owen wrote:
> > > If I were a better C coder, and had more experience with the various
> > > versions' on-disk formats, I'd be happy to try to tackle it myself.
> > > But, I'm not that great of a C coder, nor do I know the data structures
> > > well enough. Oh well.
> >
> > You would have to convert tons of rows of data in raw format. Seems
> > like dump/reload would be easier.
>
> For normal situations, it is. However, in an RPM upgrade that occurs as
> part of an OS upgrade (say, from RedHat 6.0 to RedHat 6.1), NO daemons
> can be run during a package upgrade. That doesn't seem too bad until you
> realize just what an RPM upgrade does....
Wow, doing a database upgrade inside an automated RPM. That's quite a
task. From your description, running pg_dumpall and psql to load the
data is a real chore in an automated system.
Considering the changes in aligment of row elements, and index table
changes, it would be quite difficult to write a program to convert that
data from one format to another. Not impossible, but quite hard.
--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Lamar Owen | 1999-09-08 22:07:09 | Re: [HACKERS] PG_UPGRADE status? |
Previous Message | Tom Lane | 1999-09-08 21:42:45 | Re: [HACKERS] Re: Problem enabling pltcl |