Re: Sequential scan being used despite indexes - Mailing list pgsql-performance

From James Russell
Subject Re: Sequential scan being used despite indexes
Date
Msg-id 3a3a16930601312033w2e4e3186k8f502e5b8c2cc6f2@mail.gmail.com
Whole thread Raw
In response to Re: Sequential scan being used despite indexes  (Michael Fuhr <mike@fuhr.org>)
Responses Re: Sequential scan being used despite indexes
Re: Sequential scan being used despite indexes
List pgsql-performance
[Sorry, my last reply didn't go to the list]

Reading about this issue further in the FAQ, it seems that I should ensure that Postgres has adequate and accurate information about the tables in question by regularly running VACUUM ANALYZE, something I don't do currently.

I disabled SeqScan as per the FAQ, and it indeed was a lot slower so Postgres was making the right choice in this case.

Many thanks,

James

pgsql-performance by date:

Previous
From: "Jeffrey W. Baker"
Date:
Subject: Re: Huge Data sets, simple queries
Next
From: Christopher Kings-Lynne
Date:
Subject: Re: Sequential scan being used despite indexes