Re: [HACKERS] now 6.4

From: dg(at)illustra(dot)com (David Gould)
To: maillist(at)candle(dot)pha(dot)pa(dot)us (Bruce Momjian)
Cc: hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] now 6.4
Date: 1998-06-10 19:06:42
Message-ID: 9806101906.AA02076@hawk.illustra.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> > Bruce Momjian:
> > > PG_VERSION is now 6.4. initdb everyone. Or did we decide not to do
> > > this if we could help it. I think we will still need to run initdb, and
> > > move the data files.
> >
> > I had thought we were going to avoid changing this unless there were changes
> > to persistant structures. Do you know what changed to require this?
> >
> > Thanks
>
> The contents of the system tables are going to change between releases,
> almost for sure. What I think we are going to do is have people pg_dump
> -schema their databases, mv /data to /data.old, run initdb, run to
> create the old schema, and move the data/index files back into place.
> I will probably write the script and have people test it.
>
> As long as we don't change the data/index structure, we are OK. Is that
> good, or did you think we would be able to get away without system table
> changes?

I have no problem with catalog changes and dumping the schema if we can
write a script to help them do it. I would hope we can avoid having to make
someone dump and reload their own data. I am thinking that it could be
pretty inconvenient to dump/load and reindex something like a 50GB table with
6 indexes.

Thanks for the clarification.
-dg

David Gould dg(at)illustra(dot)com 510.628.3783 or 510.305.9468
Informix Software 300 Lakeside Drive Oakland, CA 94612
- A child of five could understand this! Fetch me a child of five.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 1998-06-10 19:10:45 Re: [HACKERS] now 6.4
Previous Message Bruce Momjian 1998-06-10 18:51:56 Re: [HACKERS] now 6.4