| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: LATERAL |
| Date: | 2009-09-07 23:47:49 |
| Message-ID: | 12549.1252367269@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Mon, Sep 7, 2009 at 3:43 AM, Peter Eisentraut<peter_e(at)gmx(dot)net> wrote:
>> You could argue that the parser could infer the references and the
>> resultant join ordering restrictions automatically, but perhaps it was
>> deemed that an explicit specification would be less error-prone.
> Well, the irony is that our current code does already infer the
> references - and then disallows them.
Because as often as not, they're mistakes. Please don't think
you're smarter than the spec here.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2009-09-08 00:06:05 | Re: LATERAL |
| Previous Message | Alvaro Herrera | 2009-09-07 23:25:20 | Re: manually setting the command tag (was Re: 8.4: suppress_redundant_updates trigger vs. "Upsert" logic) |