From: Gregory Stark <stark@enterprisedb.com>
To: josh@agliodbs.com
Cc: Jim C. Nasby <jim@nasby.net>
Cc: pgsql-hackers@postgresql.org
Cc: pgsql-performance@postgresql.org
Subject: Re: [HACKERS] Hints proposal
Date: Fri, 13 Oct 2006 12:46:45 -0400
Message-ID: <87odsg17uy.fsf@enterprisedb.com> (raw)
In-Reply-To: <200610121358.22739.josh@agliodbs.com>
References: <20061012151439.GT28647@nasby.net>
<452E6FFE.7010504@agliodbs.com>
<20061012192410.GU28647@nasby.net>
<200610121358.22739.josh@agliodbs.com>
Josh Berkus <josh@agliodbs.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: stark@enterprisedb.com, josh@agliodbs.com, jim@nasby.net, pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Hints proposal
In-Reply-To: <87odsg17uy.fsf@enterprisedb.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox