From: Aaron Turner <synfinatic@gmail.com>
To: Matthew T. O'Connor <matthew@zeut.net>
Cc: pgsql-performance@postgresql.org
Subject: Re: 10+hrs vs 15min because of just one index
Date: Fri, 10 Feb 2006 09:24:39 -0800
Message-ID: <1ca1c1410602100924s191e7cddo4bda80d8f8d7cb6d@mail.gmail.com> (raw)
In-Reply-To: <43ECC9BF.2030107@zeut.net>
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/
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: synfinatic@gmail.com, matthew@zeut.net
Subject: Re: 10+hrs vs 15min because of just one index
In-Reply-To: <1ca1c1410602100924s191e7cddo4bda80d8f8d7cb6d@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox