|From:||Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>|
|To:||Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>|
|Cc:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de>, Craig Ringer <craig(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>|
|Subject:||Re: patch: function xmltable|
|Views:||Raw Message | Whole Thread | Download mbox|
2017-01-25 15:07 GMT+01:00 Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>:
> Tom Lane wrote:
> > 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
> > >> 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.
> Well, that's it. I'm not committing this patch against two other
> committers' opinion, plus I was already on the fence about the
> implementation anyway. I think you should just go with the flow and
> implement this by creating nodeTableexprscan.c. It's not even
I am sending new version - it is based on own executor scan node and
Some now obsolete regress tests removed, some new added.
The executor code (memory context usage) should be cleaned little bit - but
other code should be good.
> Álvaro Herrera https://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
|Next Message||Stephen Frost||2017-01-30 19:31:08||Re: [COMMITTERS] pgsql: test_pg_dump TAP test whitespace cleanup|
|Previous Message||Alvaro Herrera||2017-01-30 19:16:40||Re: VACUUM's ancillary tasks|