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

From Merlin Moncure
Subject Re: [HACKERS] Ongoing issues with representation of empty arrays
Date
Msg-id CAHyXU0weD_FHU1ymarG6XULjRzfbh8y_2daKUwUi=cg=rfYdZg@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 Mon, Apr 10, 2017 at 11:17 PM, 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).

Are there any impacts outside of intarray?

merlin



pgsql-hackers by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: [HACKERS] Ongoing issues with representation of empty arrays
Next
From: Michael Malis
Date:
Subject: [HACKERS] Highly Variable Planning Times