pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feed7.4 --> 8.0/8.1 upgrade
7+ messages / 6 participants
[nested] [flat]
* 7.4 --> 8.0/8.1 upgrade
@ 2006-03-29 01:47 sh test <shmailtest@yahoo.com>
0 siblings, 1 reply; 7+ messages in thread
From: sh test @ 2006-03-29 01:47 UTC (permalink / raw)
To: pgsql-admin
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.
Thanks in advance!
---------------------------------
Yahoo! Messenger with Voice. PC-to-Phone calls for ridiculously low rates.
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: 7.4 --> 8.0/8.1 upgrade
@ 2006-03-29 01:55 Scott Marlowe <smarlowe@g2switchworks.com>
parent: sh test <shmailtest@yahoo.com>
0 siblings, 2 replies; 7+ messages in thread
From: Scott Marlowe @ 2006-03-29 01:55 UTC (permalink / raw)
To: sh test <shmailtest@yahoo.com>; +Cc: pgsql-admin
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.
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: 7.4 --> 8.0/8.1 upgrade
@ 2006-03-29 03:00 Chris Travers <chris@metatrontech.com>
parent: Scott Marlowe <smarlowe@g2switchworks.com>
1 sibling, 2 replies; 7+ messages in thread
From: Chris Travers @ 2006-03-29 03:00 UTC (permalink / raw)
To: Scott Marlowe <smarlowe@g2switchworks.com>; +Cc: sh test <shmailtest@yahoo.com>; pgsql-admin
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.
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.
Best Wishes,
Chris Travers
Metatron Technology Consulting
Attachments:
chris.vcf (text/x-vcard, 169B) download
begin:vcard
fn:Chris Travers
n:Travers;Chris
email;internet:chris@metatrontech.com
tel;work:509-888-0220
tel;cell:509-630-7794
x-mozilla-html:FALSE
version:2.1
end:vcard
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: 7.4 --> 8.0/8.1 upgrade
@ 2006-03-29 09:32 Milen A. Radev <milen@radev.net>
parent: Chris Travers <chris@metatrontech.com>
1 sibling, 0 replies; 7+ messages in thread
From: Milen A. Radev @ 2006-03-29 09:32 UTC (permalink / raw)
To: 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
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: 7.4 --> 8.0/8.1 upgrade
@ 2006-03-29 15:31 Scott Marlowe <smarlowe@g2switchworks.com>
parent: Chris Travers <chris@metatrontech.com>
1 sibling, 0 replies; 7+ messages in thread
From: Scott Marlowe @ 2006-03-29 15:31 UTC (permalink / raw)
To: Chris Travers <chris@metatrontech.com>; +Cc: sh test <shmailtest@yahoo.com>; pgsql-admin
On Tue, 2006-03-28 at 21:00, Chris Travers wrote:
> 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.
>
> 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.
The only problems I've run into have been character set encoding issues,
which were fixed by iconv rather easily.
Since I set up the databases we used, and didn't inherit them, we don't
have any craziness like OIDs used as keys and such. yeah!
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: 7.4 --> 8.0/8.1 upgrade
@ 2006-03-30 22:01 Jim Nasby <jnasby@pervasive.com>
parent: Scott Marlowe <smarlowe@g2switchworks.com>
1 sibling, 1 reply; 7+ messages in thread
From: Jim Nasby @ 2006-03-30 22:01 UTC (permalink / raw)
To: Scott Marlowe <smarlowe@g2switchworks.com>; +Cc: sh test <shmailtest@yahoo.com>; pgsql-admin
On Mar 28, 2006, at 7:55 PM, 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.
Actually, there's no reason you shouldn't be able to use slony to
upgrade on the same machine, provided that machine has enough
resources to run two installs of PostgreSQL and the databases
simultaneously.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: 7.4 --> 8.0/8.1 upgrade
@ 2006-03-30 23:08 Chris Browne <cbbrowne@acm.org>
parent: Jim Nasby <jnasby@pervasive.com>
0 siblings, 0 replies; 7+ messages in thread
From: Chris Browne @ 2006-03-30 23:08 UTC (permalink / raw)
To: pgsql-admin
jnasby@pervasive.com (Jim Nasby) writes:
> On Mar 28, 2006, at 7:55 PM, 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.
>
> Actually, there's no reason you shouldn't be able to use slony to
> upgrade on the same machine, provided that machine has enough
> resources to run two installs of PostgreSQL and the databases
> simultaneously.
And note that the second instance only needs to cope with the update
traffic.
If the 7.4-based backend is servicing a lot of queries as well, that's
load that won't be on the replica.
--
(format nil "~S@~S" "cbbrowne" "acm.org")
http://www3.sympatico.ca/cbbrowne/lisp.html
"When I was a boy of fourteen, my father was so ignorant I could
hardly stand to have the old man around. But when I got to be
twenty-one, I was astonished at how much the old man had learned in
seven years." -- Mark Twain
^ permalink raw reply [nested|flat] 7+ messages in thread
end of thread, other threads:[~2006-03-30 23:08 UTC | newest]
Thread overview: 7+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2006-03-29 01:47 7.4 --> 8.0/8.1 upgrade sh test <shmailtest@yahoo.com>
2006-03-29 01:55 ` Scott Marlowe <smarlowe@g2switchworks.com>
2006-03-29 03:00 ` Chris Travers <chris@metatrontech.com>
2006-03-29 09:32 ` Milen A. Radev <milen@radev.net>
2006-03-29 15:31 ` Scott Marlowe <smarlowe@g2switchworks.com>
2006-03-30 22:01 ` Jim Nasby <jnasby@pervasive.com>
2006-03-30 23:08 ` Chris Browne <cbbrowne@acm.org>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox