Re: Improving planner variable handling

From: Gregory Stark <stark(at)enterprisedb(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Improving planner variable handling
Date: 2008-10-14 23:57:12
Message-ID: 87wsgabuhz.fsf@oxford.xeocode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:

> * When we have a non-nullable expression in a sub-select's targetlist,
> and it's below an outer join, replace the expression by
> CASE WHEN flag_var THEN original_expression ELSE NULL END
> and then flatten as normal.

I don't understand how this gets you any further ahead. Doesn't it just move
the problems you have now with the original_expression to flag_var instead?

--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's On-Demand Production Tuning

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-10-15 00:11:30 Re: Improving planner variable handling
Previous Message Tom Lane 2008-10-14 23:40:53 Bogus attribute-number range checks in spi.c