| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: what exactly is a PlaceHolderVar? |
| Date: | 2010-06-22 04:02:42 |
| Message-ID: | 23076.1277179362@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> ...but I'm still having a hard time wrapping my head around it.
The fundamental point is to be able to force a value to go to NULL
when outer-join logic says it ought to. Consider
CREATE VIEW foo AS SELECT x,y,'zed' FROM bar;
SELECT * FROM baz LEFT JOIN foo ON (baz.a = foo.x);
If you try to flatten the view then you end up with a constant 'zed'
that needs to be replaced by NULL whenever baz.a hasn't got a match
in bar.x. There's no way to make a constant go to NULL though: it's
a constant, n'est-ce pas? Instead, we have the idea of an expression
PlaceHolderVar(foo, 'zed'). This will go to null if variables from foo
ought to go to null. Otherwise it produces 'zed'. Sort of an
anti-COALESCE.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Takahiro Itagaki | 2010-06-22 04:18:31 | Re: system views for walsender activity |
| Previous Message | Andrew Dunstan | 2010-06-22 02:38:49 | Re: extensible enum types |