From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Nested CASE-WHEN scoping |
Date: | 2011-05-25 14:47:56 |
Message-ID: | 5487.1306334876@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> writes:
> While looking at fixing the multiple-evaluation issue in IN and BETWEEN
> discussed a while ago, I realized that the current assumption that only
> one CaseTestExpr placeholder needs to be valid at any given time is not
> true.
[ scratches head ... ] Why does the save/restore in ExecEvalCase not
take care of this?
> So I'm going to put the BETWEEN/IN fix aside for now, and refactor the
> placeholder infrastructure to handle several simultaneous placeholders,
That sounds like a mess, and I'm not even convinced it'll solve the
problem ...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2011-05-25 14:58:41 | Re: Expression Evaluator used for creating the plan tree / stmt ? |
Previous Message | Simon Riggs | 2011-05-25 14:41:26 | Re: use less space in xl_xact_commit patch |