Re: [PERFORM] seqscan strikes again

2004-11-11 Thread Gaetano Mendola
Jim C. Nasby wrote: > I'm wondering if there's any way I can tweak things so that the estimate > for the query is more accurate (I have run analyze): Can you post your configuration file ? I'd like to see for example your settings about: random_page_cost and effective_cache_size. Regards Gaetano M

Re: [PERFORM] seqscan strikes again

2004-11-10 Thread Jim C. Nasby
Which column would you recommend? Did something stick out at you? On Tue, Nov 09, 2004 at 03:14:36PM -0800, Joshua D. Drake wrote: > > >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 >

Re: [PERFORM] seqscan strikes again

2004-11-09 Thread Tom Lane
"Jim C. Nasby" <[EMAIL PROTECTED]> writes: > I'm wondering if there's any way I can tweak things so that the estimate > for the query is more accurate (I have run analyze): >-> Index Scan using alert__tick_tsz on alert > (cost=0.00..2498.49 rows=7119 width=28) (actual time=0.006

Re: [PERFORM] seqscan strikes again

2004-11-09 Thread Joshua D. Drake
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

[PERFORM] seqscan strikes again

2004-11-09 Thread Jim C. Nasby
I'm wondering if there's any way I can tweak things so that the estimate for the query is more accurate (I have run analyze): QUERY PLAN