Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <ringerc@ringerc.id.au>) id 1TMAxU-00079j-2p
	for pgsql-admin@postgresql.org; Thu, 11 Oct 2012 05:05:20 +0000
Received: from mail-pb0-f46.google.com ([209.85.160.46])
	by magus.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <ringerc@ringerc.id.au>) id 1TMAxS-0000j0-NP
	for pgsql-admin@postgresql.org; Thu, 11 Oct 2012 05:05:19 +0000
Received: by mail-pb0-f46.google.com with SMTP id rr4so1459113pbb.19
	for <pgsql-admin@postgresql.org>; Wed, 10 Oct 2012 22:05:17 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=message-id:date:from:user-agent:mime-version:to:cc:subject
	:references:in-reply-to:content-type:content-transfer-encoding
	:x-gm-message-state;
	bh=NQbmXyxu++oN0EzVf/q3If+/B+QZYH9XkJcUa3pGjnU=;
	b=I+IR5JvPC79Fd52DLenc5B18V8rN+7qFHjIhD2FHBt2yfbjnzxANEiNpcuasjLx3n1
	O0/f8f0YBHZCPxGQjuMeN8YU8bGsxxtGeFBKr38o5pvSlvz4v+L5NILbbTV51QW19hHN
	SvrYRwUSHur1TXtZ8TUSRdxm7eJk1268PHZ2Z28+bOrPRStN6rAJVFcw9yRB2oc7UqON
	8jZvrtjCKxUz7BSz0Z5ceiOXUuhTyHiluFC1DlQ94rXE9EATN8skRAavoPZgix3U1mmv
	zcetAFjtntMil5SCnTZC76gE1u2XBGFHw5FCbusnvmpB0cFmRAsN1wqktStaAPmojKEZ
	Kzdw==
Received: by 10.68.238.34 with SMTP id vh2mr398910pbc.6.1349931917170;
	Wed, 10 Oct 2012 22:05:17 -0700 (PDT)
Received: from ayaki.localdomain (office1.postnewspapers.com.au.
	[150.101.171.128])
	by mx.google.com with ESMTPS id s10sm1985547paz.11.2012.10.10.22.05.14
	(version=SSLv3 cipher=OTHER); Wed, 10 Oct 2012 22:05:16 -0700 (PDT)
Message-ID: <50765388.4060003@ringerc.id.au>
Date: Thu, 11 Oct 2012 13:05:12 +0800
From: Craig Ringer <ringerc@ringerc.id.au>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:14.0) Gecko/20120717 Thunderbird/14.0
MIME-Version: 1.0
To: Rosser Schwarz <rosser.schwarz@gmail.com>
CC: PgSQL ADMIN <pgsql-admin@postgresql.org>
Subject: Re: Pg 8.3.x on RHEL 6.3?
References: 
 <CAFnxYwivhRhzsA6N25pM4q267CTZ3QR51Y4Rak0=HkCbV_QOyw@mail.gmail.com>
In-Reply-To: 
 <CAFnxYwivhRhzsA6N25pM4q267CTZ3QR51Y4Rak0=HkCbV_QOyw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Gm-Message-State: 
 ALoCoQleiz9iMEdl4Ttw9tufdZ7VLCbKM+VmYSf8qckWJaMXVZOCKBmZv6wd1Y307eTG2iC7XEpt
X-Pg-Spam-Score: -1.9 (-)
X-Archive-Number: 201210/33
X-Sequence-Number: 40149

On 10/11/2012 05:15 AM, Rosser Schwarz wrote:
> 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.

I've not noticed any reports of issues specific to RHEL 6 on any version 
of Pg here, and would be surprised if any issues were to occur.

Consider retaining your old server for a little while, running as a warm 
standby with log shipping. In the exceedingly unlikely case that you do 
run into issues you can fail back to the old server.

Migrating from 8.3 to 9.1 or 9.2 isn't a big hurdle, since you're 
already past the implicit-casts-from-text stuff. About the only thing 
really likely to bite you is the bytea_output change to hex, and that's 
a trivial postgresql.conf change if you want to preserve the old 
behaviour while fixing code.

I can understand not wanting to undertake it at the same time as a 
hardware change, but you should probably schedule it for sooner rather 
than later and start testing on the new version once you're on the 
updated OS & HW.

--
Craig Ringer