Re: [HACKERS] Ongoing issues with representation of empty arrays - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [HACKERS] Ongoing issues with representation of empty arrays
Date
Msg-id CA+Tgmob4z3Aq0bBC09LBCXv2cy8zYjuNKoSuKfa7T14kyB9unw@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Ongoing issues with representation of empty arrays  (Andrew Gierth <andrew@tao11.riddles.org.uk>)
List pgsql-hackers
On Tue, Apr 11, 2017 at 12:17 AM, Andrew Gierth
<andrew@tao11.riddles.org.uk> wrote:
>>>>>> "Tom" == Tom Lane <tgl@sss.pgh.pa.us> writes:
>
>  >> First is contrib/intarray, _AGAIN_ (see past bugs such as #7730):
>  >> ...
>  >> I plan to fix this one properly, unless anyone has any objections.
>
>  Tom> Just to clarify, what do you think is "properly"?
>
> I would say, that any time an intarray function returns an empty result
> it should be the standard 0-dimensional representation that every other
> array operation uses.  The intarray functions all seem already able to
> take such values as inputs.  Also there should be regression tests for
> this (none of intarray's existing tests have any empty arrays at all).

This all sounds reasonable to me.

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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] SCRAM authentication, take three
Next
From: Heikki Linnakangas
Date:
Subject: Re: [HACKERS] SCRAM authentication, take three