aboutsummaryrefslogtreecommitdiff
path: root/src/include
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2016-08-18 14:48:51 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2016-08-18 14:48:51 -0400
commitc81c71d8846fa1667e67b45559ce4c72a8e076d9 (patch)
treea8a78134e5f1e2fde5bd22d9e82cb5828d0dfaf8 /src/include
parent191d45793df71d69b83cfa3c8c2747f7597ba1b7 (diff)
downloadpostgresql-c81c71d8846fa1667e67b45559ce4c72a8e076d9.tar.gz
postgresql-c81c71d8846fa1667e67b45559ce4c72a8e076d9.zip
In plpgsql, don't try to convert int2vector or oidvector to expanded array.
These types are storage-compatible with real arrays, but they don't support toasting, so of course they can't support expansion either. Per bug #14289 from Michael Overmeyer. Back-patch to 9.5 where expanded arrays were introduced. Report: <20160818174414.1529.37913@wrigleys.postgresql.org>
Diffstat (limited to 'src/include')
-rw-r--r--src/include/utils/array.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/include/utils/array.h b/src/include/utils/array.h
index b62b08c4824..6164f119ba7 100644
--- a/src/include/utils/array.h
+++ b/src/include/utils/array.h
@@ -36,7 +36,7 @@
*
* The OIDVECTOR and INT2VECTOR datatypes are storage-compatible with
* generic arrays, but they support only one-dimensional arrays with no
- * nulls (and no null bitmap).
+ * nulls (and no null bitmap). They don't support being toasted, either.
*
* There are also some "fixed-length array" datatypes, such as NAME and
* POINT. These are simply a sequence of a fixed number of items each