Re: UNNEST with multiple args, and TABLE with multiple funcs

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Boszormenyi Zoltan <zb(at)cybertec(dot)at>
Cc: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, PG Hackers <pgsql-hackers(at)postgresql(dot)org>, Greg Stark <stark(at)mit(dot)edu>, David Fetter <david(at)fetter(dot)org>
Subject: Re: UNNEST with multiple args, and TABLE with multiple funcs
Date: 2013-08-19 18:03:52
Message-ID: 52125E08.4020107@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 08/19/2013 09:23 AM, Boszormenyi Zoltan wrote:
>
> Indeed, it's a big nail in the coffin for SRFs-in-targetlist. Having
> WITH ORDINALITY and this feature, I would vote for removing
> SRF-in-targetlist and call the release PostgreSQL 10.0.

That's not realistic. We'd have to deprecate that syntax and
repeatedly and loudly warn people about it for at least 3 years after
the release of 9.3. You're talking about asking people to refactor
hundreds or thousands of lines of code which makes current use of things
like regex_match() in the target list.

--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2013-08-19 18:04:38 Re: danger of stats_temp_directory = /dev/shm
Previous Message Jeff Janes 2013-08-19 18:02:59 Re: pgstat_reset_remove_files ignores its argument