Re: Review: UNNEST (and other functions) WITH ORDINALITY - Mailing list pgsql-hackers

From Greg Stark
Subject Re: Review: UNNEST (and other functions) WITH ORDINALITY
Date
Msg-id CAM-w4HPKOgroCSZvwe+hP5xkpZW5f6MPRBxDHn0N8D8Gj+GLRQ@mail.gmail.com
Whole thread Raw
In response to Re: Review: UNNEST (and other functions) WITH ORDINALITY  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, Jul 24, 2013 at 6:36 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> That seems to me to be unlikely to happen, because it would be
> impossible to preserve the current (admittedly bad) semantics.
> If we're going to change the behavior at all we might as well just
> drop the feature, IMO.

It would be nice to support a single SRF in the target list. That
would side-step the bad semantics and also make it easier to
implement. But I'm not sure how easy it would be in practice because
I've learned not to underestimate the difficulty of making seemingly
small changes to the planner.


-- 
greg



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Review: UNNEST (and other functions) WITH ORDINALITY
Next
From: Tom Lane
Date:
Subject: Re: [GENERAL] Insert result does not match record count