DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=q4pisnpd/UlziFe4AI/SObONu1ho2D4WR5K+OEfsxIMGVepzXYvqoE+affOw4EawXo1o3KA3YEwI9SVE72SPLqfmjG+4eQVxK5LlrhFKThlWk9MxMS7RUgl9mil7s9NH3ttB3H+aAvfjbPWK2RE99b6oS3x99DMUMkYMzQZXafk=
Message-ID: <b41c75520805020051i4c14472ap8831dddc56a27ffd@mail.gmail.com>
Date: Fri, 2 May 2008 09:51:09 +0200
From: "Claus Guttesen" <kometen@gmail.com>
To: "Gauri Kanekar" <meetgaurikanekar@gmail.com>
Subject: Re: Pros and Cons of 8.3.1
Cc: pgsql-performance@postgresql.org
In-Reply-To: <7e4ba9550805020031l6d20b715n8f01cd5e79147dc7@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <7e4ba9550805020031l6d20b715n8f01cd5e79147dc7@mail.gmail.com>

> Can anyone who have started using 8.3.1 list out the pros and cons.

I upgraded to 8.3.1 yesterday from 8.3.0. I've used 8.3.0 since it was
released and it's working fine. I upgraded from 7.4 (dump/restore) and
it was working out of the box. We have somewhat simple sql-queries so
there was no need to change/alter these. The largest table has approx.
85 mill. records (image-table).

One thing I had newer seen before was that duplicate rows was inserted
into our order-table but I don't know whether this is due to changes
in the web-app or 8.3.0. Now that I upgraded to 8.3.1 I will wait a
few weeks and see if I get the same error before I alter the column
and add a unique contraint.

So from a 7.4-perspective and fairly simple queries I don't see any issues.

-- 
regards
Claus

When lenity and cruelty play for a kingdom,
the gentlest gamester is the soonest winner.

Shakespeare