Re: Ongoing issues with representation of empty arrays

From: Merlin Moncure <mmoncure(at)gmail(dot)com>
To: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Ongoing issues with representation of empty arrays
Date: 2017-04-19 20:36:16
Message-ID: CAHyXU0weD_FHU1ymarG6XULjRzfbh8y_2daKUwUi=cg=rfYdZg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Apr 10, 2017 at 11:17 PM, Andrew Gierth
<andrew(at)tao11(dot)riddles(dot)org(dot)uk> wrote:
>>>>>> "Tom" == Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Malis 2017-04-19 20:39:40 Highly Variable Planning Times
Previous Message David G. Johnston 2017-04-19 20:10:23 Re: Ongoing issues with representation of empty arrays