Re: best way to test new index?

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: best way to test new index?
Date: 2011-04-21 23:26:45
Message-ID: 4DB0BD35.1070600@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 4/21/11 1:28 PM, Kevin Grittner wrote:
> 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.

... And then finally, kill -9 the database server while updating the
index to test crash-safeness.

--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2011-04-21 23:27:22 Re: gincostestimate
Previous Message Josh Berkus 2011-04-21 23:21:09 Re: "stored procedures"