Re: Avoiding a seq scan on a table. - Mailing list pgsql-novice

From Alan Hodgson
Subject Re: Avoiding a seq scan on a table.
Date
Msg-id 200801140930.30967@hal.medialogik.com
Whole thread Raw
In response to Re: Avoiding a seq scan on a table.  (LWATCDR <lwatcdr@gmail.com>)
List pgsql-novice
On Monday 14 January 2008, LWATCDR <lwatcdr@gmail.com> wrote:
> Really? From what I have done in writing my own code I have found
> hashing to be faster than a btree but then when I wrote my own hashing
> it was a specific type of key.
> Anyway I put in the tree indexes and I am still getting a seq scan.
>

> Seq Scan on issuetracking  (cost=0.00..12.12 rows=1 width=0)

The planner will always choose a seq scan when your table size is very
small.

pgsql-novice by date:

Previous
From: "Sean Davis"
Date:
Subject: Re: Avoiding a seq scan on a table.
Next
From: Brian Hurt
Date:
Subject: Re: Avoiding a seq scan on a table.