Re: Sequential scan being used despite indexes

From: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
To: James Russell <internationalhobo(at)gmail(dot)com>
Cc: Michael Fuhr <mike(at)fuhr(dot)org>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Sequential scan being used despite indexes
Date: 2006-02-01 04:43:57
Message-ID: 43E03C8D.4050305@familyhealth.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

> 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.

Well then you'll get rubbish performance always in PostgreSQL...

I strongly suggest you run autovacuum if you don't really understand
PostgreSQL vacuuming/analyzing.

Chris

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Michael Fuhr 2006-02-01 05:08:28 Re: Sequential scan being used despite indexes
Previous Message James Russell 2006-02-01 04:33:08 Re: Sequential scan being used despite indexes