From: | Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Speaking of upgrades... (was Re: Predicted ...) |
Date: | 2007-01-27 03:38:51 |
Message-ID: | 45BAC94B.1050104@cox.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 01/26/07 20:12, Bruce Momjian wrote:
> Ron Johnson wrote:
>>> There is no set time frame planned that I know of.
>>>
>>> It is more a matter of users that keep the old versions alive. Some with
>>> large datasets on busy servers that can't allocate enough downtime to
>>> upgrade tend to be keeping the older versions running.
>>
>> How much does the on-disk structure of *existing* tables and indexes
>> change between x.y versions?
>>
>> Between, for example, 8.0 and 8.2?
>
> Yes:
>
> http://www.postgresql.org/docs/8.2/static/migration.html
I was thinking of something like the release notes, but a bit more
targeted. (I know. diff the source.)
http://www.postgresql.org/docs/8.2/interactive/release-8-2.html
For example, I've read these release notes, and there are some index
modifications, but don't *seem* to be *table* structure changes.
So, in an upgrade from 8.1 to 8.2, what's really preventing pg from
letting the user:
1. Cleanly shutdown pg.
2. Install v8.2.
3. Start pg.
4. psql -c 'REINDEX DATABASE' some_db
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFFuslLS9HxQb37XmcRAn90AJ4zCgRqXZbXMmWKTXWT1o7Y2c7S8ACgxYcD
maKk5w+qam1Uy8SDi/R0WQ4=
=UHLl
-----END PGP SIGNATURE-----
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2007-01-27 03:48:04 | Re: Speaking of upgrades... (was Re: Predicted ...) |
Previous Message | Bruce Momjian | 2007-01-27 02:12:42 | Re: Speaking of upgrades... (was Re: Predicted ...) |