On Thursday 21 April 2005 12:05, Enrico Weigelt wrote:
> Hi folks,
> I'm doing a simple lookup in a small table by an unique id, and I'm
> wondering, why explains tells me seqscan is used instead the key.
> The table looks like:
>     id        bigint          primary key,
>     a varchar,
>     b varchar,
>     c         varchar
> and I'm quering: select * from foo where id = 2;
> I've got only 15 records in this table, but I wanna have it as
> fast as possible since its used (as a map between IDs and names)
> for larger queries.

The over head to load the index, fetch the record in there, then check the 
table for visibility and return the value, is far greater than just doing 15 
compares in the original table.

> thx

Darcy Buskermolen
Wavefire Technologies Corp.

ph: 250.717.0200
fx: 250.763.1759

---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings

Reply via email to