Re: Closing some 8.4 open items

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Closing some 8.4 open items
Date: 2009-04-05 17:54:13
Message-ID: 603c8f070904051054u4636137bw5f8e537daa6128a@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Apr 5, 2009 at 12:21 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>> Robert Haas wrote:
>>> Well, it's a compatibility function...
>
>> compatible with what?
>
> It's required by the SQL standard.
>
>> The other thing that frankly bothers me is that we appear to have
>> acquired this function by a curious process which involved no proposal
>> or discussion that I have discovered. If there had been proper and
>> adequate discussion before the item was committed I wouldn't be making a
>> fuss now, whether or not I agreed with the result.
>
> I think Peter put it in under the assumption that meeting spec-required
> syntax would always pass muster.  It is however fair to question whether
> he made the right extrapolation of the spec's definition to cases that
> are not in the spec.
>
> Personally I am in favor of changing it to give the total number of
> array elements, on the grounds that (1) that's as defensible a reading
> of the spec as the other and (2) it would add actual new functionality
> rather than being only a relabeling of array_length.
>
> I will leave that item on the Open Items list.  I take it no one's
> excited about the others?

I'm excited about some of them, but not to the point of not wanting to
ship beta. So +1 for removing them as per your suggestions.

...Robert

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Fetter 2009-04-05 18:00:53 Re: Closing some 8.4 open items
Previous Message Stephen Frost 2009-04-05 17:46:11 Re: EXPLAIN WITH