DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=RRl+vM68HNwuX3T4FyuqV+Iz9Uyg7c2ktY/T44Qz9ub3yE9hCigwpOTD1vhYPiRObVtzjJ8V0myegJ6Trkkt9/9+XbcxMIAiKf8HTgdDnVf6LpDIbQghtBt4Z3AlBUnqkBpEr7DKhpY40DAu6k/thpaD504aDdslCu0XyqitWso=
Message-ID: <1ca1c1410602100924s191e7cddo4bda80d8f8d7cb6d@mail.gmail.com>
Date: Fri, 10 Feb 2006 09:24:39 -0800
From: Aaron Turner <synfinatic@gmail.com>
To: "Matthew T. O'Connor" <matthew@zeut.net>
Subject: Re: 10+hrs vs 15min because of just one index
Cc: pgsql-performance@postgresql.org
In-Reply-To: <43ECC9BF.2030107@zeut.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <1ca1c1410602100016p2b5fdcc4wbf45612d7efc5fdf@mail.gmail.com>
	<43ECC9BF.2030107@zeut.net>

On 2/10/06, Matthew T. O'Connor <matthew@zeut.net> wrote:
> Aaron Turner wrote:
> > So I'm trying to figure out how to optimize my PG install (8.0.3) to
> > get better performance without dropping one of my indexes.
>
> What about something like this:
>
> begin;
> drop slow_index_name;
> update;
> create index slow_index_name;
> commit;
> vacuum;

Right.  That's exactly what I'm doing to get the update to occur in 15
minutes.  Unfortunately though, I'm basically at the point of every
time I insert/update into that table I have to drop the index which is
making my life very painful (having to de-dupe records in RAM in my
application is a lot faster but also more complicated/error prone).

Basically, I need some way to optimize PG so that I don't have to drop
that index every time.

Suggestions?

--
Aaron Turner
http://synfin.net/