| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Craig Ringer <craig(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: patch: function xmltable |
| Date: | 2017-01-25 04:45:03 |
| Message-ID: | 16622.1485319503@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2017-01-24 21:32:56 -0300, Alvaro Herrera wrote:
>> XMLTABLE is specified by the standard to return multiple rows ... but
>> then as far as my reading goes, it is only supposed to be supported in
>> the range table (FROM clause) not in the target list. I wonder if
>> this would end up better if we only tried to support it in RT. I asked
>> Pavel to implement it like that a few weeks ago, but ...
> Right - it makes sense in the FROM list - but then it should be an
> executor node, instead of some expression thingy.
+1 --- we're out of the business of having simple expressions that
return rowsets.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2017-01-25 04:45:24 | Re: patch: function xmltable |
| Previous Message | Jim Nasby | 2017-01-25 04:43:27 | Re: Faster methods for getting SPI results (460% improvement) |