Re: 8.3b1 in production? - Mailing list pgsql-general

From Gregory Stark
Subject Re: 8.3b1 in production?
Date
Msg-id 87d4v3t9yc.fsf@oxford.xeocode.com
Whole thread Raw
In response to Re: 8.3b1 in production?  ("Scott Marlowe" <scott.marlowe@gmail.com>)
List pgsql-general
"Scott Marlowe" <scott.marlowe@gmail.com> writes:

> On 10/25/07, Peter Childs <peterachilds@gmail.com> wrote:
>> I was wondering why my PITR base back up was taking 2 hours on my 8.3 test
>> database where as it takes 50 minutes on 8.1 and the database files are
>> meant to be smaller on a freshly installed 8.3 server rather than a 8.1.1
>> server that aint been rebuilt since 8.1.1 was newly out.
>> I was planning to upgrade to 8.3 once its out...
>>
>> Down time for upgrades is somwhat lacking in a 24x7 business.
>>
>> Oh my 8.1 server has been up for well over a year with out being down at
>> all. the database for longer which really show how good postgres really is
>> 377 days uptime on computer and I think that was to move a plug.
>
> You should really look at scheduling the 5 minute window up update
> your 8.1 install.  8.1.1 is quite old and has a few known data eating
> bugs, if I remember correctly.  Updating to 8.1.10 should only take
> literally about 1 or 2 minutes.

Actually 8.1.2 fixed two locale problems which could require reindexing. If
you're using plperl functions which play with the locale or a locale like
hungarian which compares some different strings as equal then you might have
to reindex.

Otherwise it's just a Postgres server restart's worth of downtime. There are
both data eating bug fixes and security fixes in 8.1.10 for you.

--
  Gregory Stark
  EnterpriseDB          http://www.enterprisedb.com

pgsql-general by date:

Previous
From: Ralph Smith
Date:
Subject: 2 versions running & using pg_dumpall
Next
From: Tom Lane
Date:
Subject: Re: select count() out of memory