| From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
|---|---|
| To: | josh(at)agliodbs(dot)com |
| Cc: | "Jim C(dot) Nasby" <jim(at)nasby(dot)net>, pgsql-hackers(at)postgresql(dot)org, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: [HACKERS] Hints proposal |
| Date: | 2006-10-13 16:46:45 |
| Message-ID: | 87odsg17uy.fsf@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-performance |
Josh Berkus <josh(at)agliodbs(dot)com> writes:
>> > I actually think the way to attack this issue is to discuss the kinds
>> > of errors the planner makes, and what tweaks we could do to correct
>> > them. Here's the ones I'm aware of:
>> >
>> > -- Incorrect selectivity of WHERE clause
>> > -- Incorrect selectivity of JOIN
>> > -- Wrong estimate of rows returned from SRF
>> > -- Incorrect cost estimate for index use
>> >
>> > Can you think of any others?
-- Incorrect estimate for result of DISTINCT or GROUP BY.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2006-10-13 17:00:29 | Re: [PERFORM] Hints proposal |
| Previous Message | Jeff Davis | 2006-10-13 16:45:54 | Re: [PERFORM] Hints proposal |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2006-10-13 17:00:29 | Re: [PERFORM] Hints proposal |
| Previous Message | Jeff Davis | 2006-10-13 16:45:54 | Re: [PERFORM] Hints proposal |