Re: proposal: searching in array function - array_position - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: proposal: searching in array function - array_position
Date
Msg-id 20150318010627.GR3636@alvh.no-ip.org
Whole thread Raw
In response to Re: proposal: searching in array function - array_position  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: proposal: searching in array function - array_position
List pgsql-hackers
My main question regarding this patch is whether the behavior with MD
arrays is useful at all.  Suppose I give it this:

alvherre=# select array_offset('{{{1,2},{3,4},{5,6}},{{2,3},{4,5},{6,7}}}', 3);
 array_offset
--------------
            3
(1 fila)

What can I do with the "3" value it returned?  Certainly not use it as
an offset to get a slice of the original array.  The only thing that
seems sensible to me here is to reject the whole thing with an error,
that is, only accept 1-D arrays here.  We can later extend the function
by allowing higher dimensionality as long as the second argument is an
array one dimension less than the first argument.  But if we allow the
case on its appearance, it's going to be difficult to change the
behavior later.

Has a case been made for the current behavior?

--
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Strange assertion using VACOPT_FREEZE in vacuum.c
Next
From: Alvaro Herrera
Date:
Subject: Re: Strange assertion using VACOPT_FREEZE in vacuum.c