Re: Hypothetical suggestions for planner, indexing improvement

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: pgsql-performance <pgsql-performance(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Hypothetical suggestions for planner, indexing improvement
Date: 2003-05-06 04:45:30
Message-ID: 22400.1052196330@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-performance

Josh Berkus <josh(at)agliodbs(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Mario Caspari 2003-05-06 06:23:27 Installin Postgres
Previous Message Josh Berkus 2003-05-06 04:33:33 Re: Hypothetical suggestions for planner, indexing improvement

Browse pgsql-performance by date

  From Date Subject
Next Message Reiner Dassing 2003-05-06 06:59:43 Select on timestamp-day slower than timestamp alone
Previous Message Josh Berkus 2003-05-06 04:33:33 Re: Hypothetical suggestions for planner, indexing improvement