Re: proposal: fix corner use case of variadic fuctions usage - Mailing list pgsql-hackers

From Robert Haas
Subject Re: proposal: fix corner use case of variadic fuctions usage
Date
Msg-id CA+TgmobSq5m5Cbkb3gmrbYSPLvtQ9NmZkqGh_mS46h_Znd36bQ@mail.gmail.com
Whole thread Raw
In response to Re: proposal: fix corner use case of variadic fuctions usage  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: proposal: fix corner use case of variadic fuctions usage
List pgsql-hackers
On Sat, Jan 19, 2013 at 3:27 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> disagree - non variadic manner call should not be used for walk around
>> FUNC_MAX_ARGS limit. So there should not be passed big array.
>
> That's utter nonsense.  Why wouldn't people expect concat(), for
> example, to work for large (or even just moderate-sized) arrays?

/me blinks.

What does that have to do with anything?  IIUC, the question isn't
whether CONCAT() would work for large arrays, but rather for very
large numbers of arrays written out as CONCAT(a1, ..., a10000000).

I don't understand why an appropriately-placed check against
FUNC_MAX_ARGS does anything other than enforce a limit we already
have.  Or are we currently not consistently enforcing that limit?

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: proposal: fix corner use case of variadic fuctions usage
Next
From: Stephen Frost
Date:
Subject: Re: Further pg_upgrade analysis for many tables