Re: best way to test new index? - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: best way to test new index?
Date
Msg-id 4DB04D1C020000250003CB73@gw.wicourts.gov
Whole thread Raw
In response to Re: best way to test new index?  (Yves Weißig <weissig@rbg.informatik.tu-darmstadt.de>)
Responses Re: best way to test new index?  (Josh Berkus <josh@agliodbs.com>)
List pgsql-hackers
Yves Weißig<weissig@rbg.informatik.tu-darmstadt.de> wrote:
> Am 21.04.2011 20:56, schrieb Kevin Grittner:
>> Yves Weißig<weissig@rbg.informatik.tu-darmstadt.de> wrote:
>>  
>>> what is the best way to test a new developed index structure?
>>  
>> Are you talking about a new AM (like btree, hash, GiST, or GIN)?
> 
> Yes I do!
The tests are going to depend somewhat on what the index is intended
to do.
That said, I would start by making sure that basic things like
CREATE INDEX and DROP INDEX work.  Then I would test that INSERT,
UPDATE, and DELETE do the right things with the index.  Then I would
make sure that vacuum did the right thing.  Then I would make sure
that the optimizer was doing a reasonable job of knowing when it was
usable and what it cost, so that it would be chosen when
appropriate.  Once everything seemed to be behaving I would
benchmark it against the reasonable alternatives.
-Kevin


pgsql-hackers by date:

Previous
From: Merlin Moncure
Date:
Subject: Re: "stored procedures"
Next
From: Bruce Momjian
Date:
Subject: Patch for pg_upgrade to turn off autovacuum