Re: Optimization with dates

From: "Josh Berkus" <josh(at)agliodbs(dot)com>
To: Jean-Christophe Boggio <cat(at)thefreecat(dot)org>, pgsql-sql(at)postgresql(dot)org
Subject: Re: Optimization with dates
Date: 2001-11-14 00:19:13
Message-ID: web-505462@davinci.ethosmedia.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

Jean-Christophe,

> Aggregate (cost=256546.78..256546.78 rows=1 width=0)
> -> Seq Scan on gains (cost=0.00..250627.68 rows=2367640 width=0)
>
> whereas :

Hmmm... if the number of rows is actually accurate (2M out of 10M in the
last 30 days) then a Seq Scan seems like a good plan to me. If the
numbers aren't accurate, it's time to run a VACUUM ANALYZE.

Regardless, if you're actually querying for 2M recordsets, you'd better
throw some hardware at the problem, and learn the .conf parameters.

-Josh

______AGLIO DATABASE SOLUTIONS___________________________
Josh Berkus
Complete information technology josh(at)agliodbs(dot)com
and data management solutions (415) 565-7293
for law firms, small businesses fax 621-2533
and non-profit organizations. San Francisco

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Jason Earl 2001-11-14 00:44:00 Re: Optimization with dates
Previous Message Stephan Szabo 2001-11-14 00:17:06 Re: Optimization with dates