Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: [HACKERS] Hints proposal
- From: Gregory Stark <stark(at)enterprisedb(dot)com>
- To: josh(at)agliodbs(dot)com
- Cc: "Jim C. Nasby" <jim(at)nasby(dot)net>, pgsql-hackers(at)postgresql(dot)org, pgsql-performance(at)postgresql(dot)org
- Subject: Re: [HACKERS] Hints proposal
- Date: Fri, 13 Oct 2006 12:46:45 -0400
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
- Follow-Ups:
- Re: [HACKERS] Hints proposal
- From: Robert Treat
- Re: [HACKERS] Hints proposal
- References:
- Hints proposal
- From: Jim C. Nasby
- Re: [HACKERS] Hints proposal
- From: Josh Berkus
- Re: [HACKERS] Hints proposal
- From: Jim C. Nasby
- Re: [HACKERS] Hints proposal
- From: Josh Berkus
- Hints proposal
- Prev by Date: Re: [HACKERS] Hints proposal
- Next by Date: Re: [HACKERS] Hints proposal
- Previous by thread: Re: [HACKERS] Hints proposal
- Next by thread: Re: [HACKERS] Hints proposal
- Indexes: