Text Size: Normal / Large

9.17. Array Functions and Operators

Table 9-40 shows the operators available for array types.

Table 9-40. Array Operators

OperatorDescriptionExampleResult
= equalARRAY[1.1,2.1,3.1]::int[] = ARRAY[1,2,3]t
<> not equalARRAY[1,2,3] <> ARRAY[1,2,4]t
< less thanARRAY[1,2,3] < ARRAY[1,2,4]t
> greater thanARRAY[1,4,3] > ARRAY[1,2,4]t
<= less than or equalARRAY[1,2,3] <= ARRAY[1,2,3]t
>= greater than or equalARRAY[1,4,3] >= ARRAY[1,4,3]t
@> containsARRAY[1,4,3] @> ARRAY[3,1]t
<@ is contained byARRAY[2,7] <@ ARRAY[1,7,4,2,6]t
&& overlap (have elements in common)ARRAY[1,4,3] && ARRAY[2,1]t
|| array-to-array concatenationARRAY[1,2,3] || ARRAY[4,5,6]{1,2,3,4,5,6}
|| array-to-array concatenationARRAY[1,2,3] || ARRAY[[4,5,6],[7,8,9]]{{1,2,3},{4,5,6},{7,8,9}}
|| element-to-array concatenation3 || ARRAY[4,5,6]{3,4,5,6}
|| array-to-element concatenationARRAY[4,5,6] || 7{4,5,6,7}

Array comparisons compare the array contents element-by-element, using the default B-Tree comparison function for the element data type. In multidimensional arrays the elements are visited in row-major order (last subscript varies most rapidly). If the contents of two arrays are equal but the dimensionality is different, the first difference in the dimensionality information determines the sort order. (This is a change from versions of PostgreSQL prior to 8.2: older versions would claim that two arrays with the same contents were equal, even if the number of dimensions or subscript ranges were different.)

See Section 8.14 for more details about array operator behavior.

Table 9-41 shows the functions available for use with array types. See Section 8.14 for more information and examples of the use of these functions.

Table 9-41. Array Functions

FunctionReturn TypeDescriptionExampleResult
array_append(anyarray, anyelement) anyarrayappend an element to the end of an arrayarray_append(ARRAY[1,2], 3){1,2,3}
array_cat(anyarray, anyarray) anyarrayconcatenate two arraysarray_cat(ARRAY[1,2,3], ARRAY[4,5]){1,2,3,4,5}
array_ndims(anyarray) intreturns the number of dimensions of the arrayarray_ndims(ARRAY[[1,2,3], [4,5,6]])2
array_dims(anyarray) textreturns a text representation of array's dimensionsarray_dims(ARRAY[[1,2,3], [4,5,6]])[1:2][1:3]
array_fill(anyelement, int[], [, int[]]) anyarrayreturns an array initialized with supplied value and dimensions, optionally with lower bounds other than 1array_fill(7, ARRAY[3], ARRAY[2])[2:4]={7,7,7}
array_length(anyarray, int) intreturns the length of the requested array dimensionarray_length(array[1,2,3], 1)3
array_lower(anyarray, int) intreturns lower bound of the requested array dimensionarray_lower('[0:2]={1,2,3}'::int[], 1)0
array_prepend(anyelement, anyarray) anyarrayappend an element to the beginning of an arrayarray_prepend(1, ARRAY[2,3]){1,2,3}
array_to_string(anyarray, text) textconcatenates array elements using supplied delimiterarray_to_string(ARRAY[1, 2, 3], '~^~')1~^~2~^~3
array_upper(anyarray, int) intreturns upper bound of the requested array dimensionarray_upper(ARRAY[1,2,3,4], 1)4
string_to_array(text, text) text[]splits string into array elements using supplied delimiterstring_to_array('xx~^~yy~^~zz', '~^~'){xx,yy,zz}
unnest(anyarray) setof anyelementexpand an array to a set of rowsunnest(ARRAY[1,2])1

2

(2 rows)

See also Section 9.18 about the aggregate function array_agg for use with arrays.


User Comments


Photo Researchers
19 Jan 2010 19:20:16

unnest() when paired with another unnest() in the same SELECT statement behaves very differently depending on whether the arrays have the same [flattened] dimensions or not.  Compare:

SELECT unnest(ARRAY[1,2]) AS a,unnest(ARRAY[3,4]) AS b;
a | b
---+---
1 | 3
2 | 4
(2 rows)

SELECT unnest(ARRAY[1,2]) AS a,unnest(ARRAY[3,4,5]) AS b;
a | b
---+---
1 | 3
2 | 4
1 | 5
2 | 3
1 | 4
2 | 5
(6 rows)

It makes sense from a certain perspective -- only the cross-product makes sense for differing dimensions -- but the inconsistent behavior is icky and should be better documented here.

Photo Researchers
21 Jan 2010 1:19:35

unnest() when paired with another unnest() in the same SELECT statement behaves very differently depending on whether the arrays have the same [flattened] dimensions or not.  Compare:

SELECT unnest(ARRAY[1,2]) AS a,unnest(ARRAY[3,4]) AS b;
a | b
---+---
1 | 3
2 | 4
(2 rows)

SELECT unnest(ARRAY[1,2]) AS a,unnest(ARRAY[3,4,5]) AS b;
a | b
---+---
1 | 3
2 | 4
1 | 5
2 | 3
1 | 4
2 | 5
(6 rows)

It makes sense from a certain perspective -- only the cross-product makes sense for differing dimensions -- but the inconsistent behavior is icky and should be better documented here.

Add Comment

Please use this form to add your own comments regarding your experience with particular features of PostgreSQL, clarifications of the documentation, or hints for other users. Please note, this is not a support forum, and your IP address will be logged. If you have a question or need help, please see the faq, try a mailing list, or join us on IRC. Note that submissions containing URLs or other keywords commonly found in 'spam' comments may be silently discarded. Please contact the webmaster if you think this is happening to you in error.

In order to submit a comment, you must have a community account.

* Comment
 

* denotes required field

Privacy Policy | Project hosted by our server sponsors. | Designed by tinysofa
Copyright © 1996 – 2010 PostgreSQL Global Development Group