Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 2D75C63248A for ; Thu, 22 Jan 2009 15:44:13 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 43915-06 for ; Thu, 22 Jan 2009 15:44:08 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.31]) by mail.postgresql.org (Postfix) with ESMTP id 6FE7E63242D for ; Thu, 22 Jan 2009 15:44:06 -0400 (AST) Received: by yw-out-2324.google.com with SMTP id 3so1784611ywj.73 for ; Thu, 22 Jan 2009 11:44:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=xLkQLb2qPfHkPDrBWGkl9I28CEBiwXl6AnCqFQN3XMI=; b=FHljaL41OUP/6UzVAyN2jtd81B7mn90XxEW6zyOlu+bR30hYkmU9DUtzq6PXLGPJk1 lkE/dR9YeaXFWxFJwlmpwAiKL0exUDr09THklztU46VdytlSaJcxTSpMhAu31KENHg48 b2FjhEGdHTRVzbvC3hNDijLhP2X9Xdgrc+AYs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=DnkrH8Acd7YlBrDxQVJS6M8ONuznOkFjsht6T3Ma+recKtNbk7S3IovBas2N1Xe/jj +RJwOLiJbO7NF/iY3dA1MjYo26VO+B/WeOOyYfsbAKlAgTNc01QKh8lbmmYdv+OmSIpo 3uXgSi+dht/3rVR8sqopzlvFdu2m9Oe/j4RvU= MIME-Version: 1.0 Received: by 10.151.27.9 with SMTP id e9mr1690768ybj.42.1232653445472; Thu, 22 Jan 2009 11:44:05 -0800 (PST) In-Reply-To: <288819.46212.qm@web111306.mail.gq1.yahoo.com> References: <288819.46212.qm@web111306.mail.gq1.yahoo.com> Date: Thu, 22 Jan 2009 12:44:05 -0700 Message-ID: Subject: Re: Postgres 8.3.x upgrade From: Scott Marlowe To: Jessica Richard Cc: pgsql-admin@postgresql.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200901/129 X-Sequence-Number: 31176 On Thu, Jan 22, 2009 at 7:50 AM, Jessica Richard wrote: > We are going to upgrade our Postgres servers (most 8.2.9 and some 8.2.4) to > the 8.3.x version. > > From the postgres web site, I can see the 8.3.5 is the latest version. > > Question for people who have been on 8.3.5: > > Is 8.3.5 very safe to use (no major new bugs)? Is it really better than the > older versions of the 8.3.X families? We've been running it in production since last fall and 8.3.x is a very stable and very fast branch. We had about ten or so queries that failed due to bad casting, that we fixed in about a day. Upgrading postgres, even counting these small issues, is one of the least painful upgrades I've ever done. As for 8.3.x with x being 0 through 5 right now, the newer versions are bug and security fixes only over 8.3.0. You want those bug fixes, and running an older update version (i.e. 8.3.1) versus the latest (i.e. 8.3.5) is rarely a good idea. Unlike some database products which are known to ship later versions that break things (**cough** MySQL **cough**) the postgresql hackers are VERY picky about what goes into a point update. **cough** (see http://bugs.mysql.com/bug.php?id=31001 )