Re: Speaking of upgrades... (was Re: Predicted ...) - Mailing list pgsql-general

From Ron Johnson
Subject Re: Speaking of upgrades... (was Re: Predicted ...)
Date
Msg-id 45BAD227.5080202@cox.net
Whole thread Raw
In response to Re: Speaking of upgrades... (was Re: Predicted ...)  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Speaking of upgrades... (was Re: Predicted ...)
Re: Speaking of upgrades... (was Re: Predicted ...)
List pgsql-general
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 01/26/07 21:48, Bruce Momjian wrote:
> Ron Johnson wrote:
>>> 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
>
> The changes are usually very subtle, like changes in the storage format
> for certain data types, or bit changes in the row headers --- it isn't
> something really of interest except to developers.

Ah, too low-level to make it into the relnotes.

What are your plans for reducing the number of resources needed to
upgrade databases?


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFFutInS9HxQb37XmcRAsihAKC+j6D4HVkWqc4l9EctRuHfud0WDgCghGZ6
a2W1ym+Fru3YowebTLgCqto=
=+K4E
-----END PGP SIGNATURE-----

pgsql-general by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Speaking of upgrades... (was Re: Predicted ...)
Next
From: "Joshua D. Drake"
Date:
Subject: Re: Speaking of upgrades... (was Re: Predicted ...)