Re: why Sequencial Scan when selecting on primary key of table? - Mailing list pgsql-performance

From Andrew Sullivan
Subject Re: why Sequencial Scan when selecting on primary key of table?
Date
Msg-id 20030531170205.GD22469@libertyrms.info
Whole thread Raw
In response to why Sequencial Scan when selecting on primary key of table?  ("Brian Tarbox" <btarbox@theworld.com>)
List pgsql-performance
On Sat, May 31, 2003 at 12:30:40PM -0400, Brian Tarbox wrote:
> I have a simple table with a dozen integer fields and a primary key.
>
> When I say "explain select * from Patient where Patient_primary_key = 100"
>
> I get sequential scan.
>
> I've just converted my application from MySQL and am seeing everything run
> about 3X slower.  What do I have to do to get postgres to use indexes?

Usual questions: have you vacuumed?  EXPLAIN ANALYSE output, schema,
&c.

A

--
----
Andrew Sullivan                         204-4141 Yonge Street
Liberty RMS                           Toronto, Ontario Canada
<andrew@libertyrms.info>                              M2P 2A8
                                         +1 416 646 3304 x110


pgsql-performance by date:

Previous
From: "Brian Tarbox"
Date:
Subject: why Sequencial Scan when selecting on primary key of table?
Next
From: Tom Lane
Date:
Subject: Re: why Sequencial Scan when selecting on primary key of table?