Re: 10+hrs vs 15min because of just one index

From: Aaron Turner <synfinatic(at)gmail(dot)com>
To: "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: 10+hrs vs 15min because of just one index
Date: 2006-02-10 17:24:39
Message-ID: 1ca1c1410602100924s191e7cddo4bda80d8f8d7cb6d@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On 2/10/06, Matthew T. O'Connor <matthew(at)zeut(dot)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/

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Ron 2006-02-10 19:22:31 What do the Windows pg hackers out there like for dev tools?
Previous Message Matthew T. O'Connor 2006-02-10 17:13:35 Re: 10+hrs vs 15min because of just one index