From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Sort of a planner regression 8.3->8.4 (due to EXISTS inlining) and related stuff |
Date: | 2010-05-17 02:40:36 |
Message-ID: | 201005170440.38450.andres@anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Monday 17 May 2010 04:10:46 Tom Lane wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> > I believe this is a result of a limitation we've discussed
> > previously, namely, that the planner presently uses a limited,
> > special-case kludge to consider partial index scans, and the executor
> > uses another kludge to execute them.
> It may be worth pointing out that while the current code sucks for the
> case where a nestloop-with-inner-indexscan would be the best plan, the
> previous code sucked for every other case; because the previous code was
> only capable of generating the equivalent of a nestloop join. We have
> to continue down this path in order to get to the place we need to be.
> It's too bad that all the work didn't get done in one development cycle,
> but sometimes life's like that.
Yes, I realize that. Thats why I didnt report it as an actual bug... And its
way easier to deal with 8.4s "deficiency" than with the former behaviour.
Thanks,
Andres
PS: I think it lead me to an actual bug, expect a report tomorrow...
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-05-17 02:44:51 | Re: pg_upgrade and extra_float_digits |
Previous Message | Andrew Dunstan | 2010-05-17 02:37:49 | Re: pg_upgrade and extra_float_digits |