From: | borz_off(at)cs(dot)msu(dot)su |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | BUG #8399: inconsistent input of multidimensional arrays |
Date: | 2013-08-27 08:18:10 |
Message-ID: | E1VEETa-0007KM-8O@wrigleys.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 8399
Logged by: Alexey Borzov
Email address: borz_off(at)cs(dot)msu(dot)su
PostgreSQL version: 9.3rc1
Operating system: irrelevant
Description:
PostgreSQL documentation states:
"Multidimensional arrays must have matching extents for each dimension. A
mismatch causes an error..."
This is not completely true:
postgres=# select cast('{{1,2}, {3}}' as integer[]);
ERROR: multidimensional arrays must have array expressions with matching
dimensions
LINE 1: select cast('{{1,2}, {3}}' as integer[]);
^
postgres=# select cast('{{1}, {2,3}}' as integer[]);
int4
------------------
{{1,NULL},{2,3}}
(1 row)
Trying to use an array constructor yields an expected error in both cases.
Confirmed on 9.3rc1 and 9.0.13
From | Date | Subject | |
---|---|---|---|
Next Message | ajayaksadvance | 2013-08-27 08:31:30 | BUG #8400: DB size changed after restore |
Previous Message | martin.kevin | 2013-08-26 18:00:37 | BUG #8398: to_json(''::hstore) gives invalid JSON |