From: Tom Lane <tgl@sss.pgh.pa.us>
To: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-performance <pgsql-performance@postgresql.org>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Hypothetical suggestions for planner, indexing improvement
Date: Tue, 06 May 2003 00:45:30 -0400
Message-ID: <22400.1052196330@sss.pgh.pa.us> (raw)
In-Reply-To: <200305052133.33680.josh@agliodbs.com>
References: <200305051219.58955.josh@agliodbs.com>
<22292.1052195133@sss.pgh.pa.us>
<200305052133.33680.josh@agliodbs.com>
Josh Berkus <josh@agliodbs.com> writes:
> The reason that I mention EXISTS is because that's where the lack of
> cross-column corellation is most dramatic; the planner seems to estimate a
> flat 50% for EXISTS clauses regardless of the content.
No "seems to" about that one: see src/backend/optimizer/path/clausesel.c
else if (is_subplan(clause))
{
/*
* Just for the moment! FIX ME! - vadim 02/04/98
*/
s1 = (Selectivity) 0.5;
}
Patches to improve this are welcome ;-). But I'm not at all sure how to
write something that would extract a reliable selectivity estimate from
a subplan.
regards, tom lane
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, josh@agliodbs.com, pgsql-hackers@postgresql.org
Subject: Re: Hypothetical suggestions for planner, indexing improvement
In-Reply-To: <22400.1052196330@sss.pgh.pa.us>
References: <200305051219.58955.josh@agliodbs.com> <22292.1052195133@sss.pgh.pa.us> <200305052133.33680.josh@agliodbs.com> <22400.1052196330@sss.pgh.pa.us>
* 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