Ok, but I thought more like an automated test, or a test which checks if
the interface is correctly implemented. By the way, tho broaden the
topic, what would be the best way to debug in pg? elog? asserts?
Am 22.04.2011 01:26, schrieb Josh Berkus:
> 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.
>
