From: | "Milen A(dot) Radev" <milen(at)radev(dot)net> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: 7.4 --> 8.0/8.1 upgrade |
Date: | 2006-03-29 09:32:31 |
Message-ID: | e0dk7e$1si$1@sea.gmane.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Chris Travers написа:
> Scott Marlowe wrote:
>
>> On Tue, 2006-03-28 at 19:47, sh test wrote:
>>
>>
>>> Hello admins!
>>>
>>> i need to collect as much information
>>>
>>> pro/cons on a possible upgrade from
>>>
>>> 7.4 ---> 8.0/8.1 version
>>>
>>> Aside from getting our users vote on this, I wanted to ask you first
>>> in order to collect any possible issues one might run into from
>>> upgrading to such
>>> versions.
>>>
>>
>> Downside: You gotta dump and reload, or use slony to minimize the
>> downtime, but you need a spare machine to do that.
>> Upside: Everything else. PostgreSQL 8.x series has a lot of
>> performance improvements.
>>
>>
> When I upgraded from 7.4.2 to 8.1.3, I lost the oid fields in some
> tables which caused some issues with one application.
Probably because in 8.1 the value for the "default_with_oids" parameter
is "false". If you had tried to set it to "true" (at least for duration
of the restore) then you would have not lost those OIDs.
>
> I suspect that the better path is to upgrade (without dump/reload) to
> the most recent 7.4 release and then dump/reload when upgrading to 8.1.x
> but I am not 100% sure.
>
> If you don't WANT OID's in your table (they were dropped for a reason,
> you know), then this is not a concern.
--
Milen A. Radev
From | Date | Subject | |
---|---|---|---|
Next Message | Gourish Singbal | 2006-03-29 10:06:36 | auto vacuuming |
Previous Message | Chris Travers | 2006-03-29 03:00:32 | Re: 7.4 --> 8.0/8.1 upgrade |