diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2016-08-18 14:48:51 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2016-08-18 14:49:08 -0400 |
| commit | 5697522d8411135d26a5d807f9e4afa182502f64 (patch) | |
| tree | dbbb00f7c418fcab13cb5e9082338f2574117f3e /src/include/utils/array.h | |
| parent | e8306745e3504c642f7abad411139d5630e29fac (diff) | |
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/utils/array.h')
| -rw-r--r-- | src/include/utils/array.h | 2 |
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 |