| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PgSQL Performance ML <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Suggestions wanted for 7.2.4 query |
| Date: | 2003-05-05 17:59:11 |
| Message-ID: | 200305051059.11751.josh@agliodbs.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Folks,
> That may be solvable without forcing a seq scan on "events", simply by
> overdetermining the criteria on date. That is, I can't apply the date
> criteria to "events" because that would require running date calucations on
> each row forcing a seq scan ( i.e. (event_date + duration) between date_one
> and date_two would require a seq scan), but I can apply a broadend version
of
> the criteria to "events" ( i.e. event_date between (date_one - 1 month) and
> (date_two + 1 day)) which would give the planner the idea that it is
> returning a minority of rows from "events".
If anyone is interested, the above idea worked.
--
-Josh Berkus
Aglio Database Solutions
San Francisco
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Achilleus Mantzios | 2003-05-05 18:38:43 | Re: [SQL] Indices are not used by the optimizer |
| Previous Message | scott.marlowe | 2003-05-05 16:38:03 | Re: Looking for a cheap upgrade (RAID) |