To: pgsql-admin@postgresql.org
From: Walter Hurry <walterhurry@gmail.com>
Subject: Re: Pg 8.3.x on RHEL 6.3?
Date: Wed, 10 Oct 2012 23:12:26 +0000 (UTC)
Lines: 25
Message-ID: <k54vcq$3nb$1@ger.gmane.org>
References: 
 <CAFnxYwivhRhzsA6N25pM4q267CTZ3QR51Y4Rak0=HkCbV_QOyw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
User-Agent: Pan/0.135 (Tomorrow I'll Wake Up and Scald Myself with Tea; GIT
	30dc37b master)

On Wed, 10 Oct 2012 14:15:15 -0700, Rosser Schwarz wrote:

> Fellow Pg Admins,
> 
> At $work, we're preparing to move one of our Pg instances to new
> hardware, and considering an OS upgrade at the same time.  The instance
> in question is running an older version of 8.3, which we'd like to
> upgrade to 8.3.latest (presently .21; unf., we don't have the time or
> testing resources to migrate to a more recent major release of postgres
> as well).
> 
> In preparation for that effort, I've been asked to avail myself of the
> collective experience and wisdom of the wider community to see if anyone
> has seen anything unexpected, or any kind of misbehavior in running 8.3
> on RHEL 6.3.  None of my research suggests we should have any problems,
> but for sake of due diligence and checking the box, I'm soliciting any
> input anyone with experience with this configuration might be able to
> offer.  We aren't doing anything that would subject us to the
> referential_constraints issue, fixed in 8.3.17.
> 
> Can we expect to see any benefit from the llseek kernel changes with
> 8.3, or is the upside of that more limited to people also running 9.2?
> 

OK, I'll do your work for you. $200/hr.