| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | "Jim C(dot) Nasby" <decibel(at)decibel(dot)org> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: seqscan strikes again |
| Date: | 2004-11-09 23:14:36 |
| Message-ID: | 41914F5C.9030505@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
> opensims=#
>
> I'd really like to avoid putting a 'set enable_seqscan=false' in my
> code, especially since this query only has a problem if it's run on a
> large date/time window, which normally doesn't happen.
Try increasing your statistics target for the column and then rerunning
analyze.
Sincerely,
Joshua D. Drake
--
Command Prompt, Inc., home of PostgreSQL Replication, and plPHP.
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-667-4564 - jd(at)commandprompt(dot)com - http://www.commandprompt.com
Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL
| Attachment | Content-Type | Size |
|---|---|---|
| jd.vcf | text/x-vcard | 640 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-11-09 23:24:32 | Re: seqscan strikes again |
| Previous Message | Sean Chittenden | 2004-11-09 22:44:00 | Re: Need advice on postgresql.conf settings |