diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2014-05-05 13:37:54 -0400 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2014-05-05 13:37:54 -0400 |
commit | 3727afafeef69088456acc3f6257360315220a20 (patch) | |
tree | 471bbbd54c2312136216a11a1fca98a374caee0b /src/backend/utils/adt/arrayutils.c | |
parent | b2f7bd72c4d3e80065725c72e85778d5f4bdfd4a (diff) | |
download | postgresql-3727afafeef69088456acc3f6257360315220a20.tar.gz postgresql-3727afafeef69088456acc3f6257360315220a20.zip |
Fix pg_type.typlen for newly-revived line type.
Commit 261c7d4b653bc3e44c31fd456d94f292caa50d8f removed the "m" field
from struct LINE, but neglected to make pg_type.h's idea of the type's
size match. This resulted in reading past the end of palloc'd LINE
values when inserting them into tuples etc. In principle that could
cause a SIGSEGV, though the odds of detectable problems seem low.
Bump catversion since this makes an incompatible on-disk format change.
Note that if the line type had been in use in the field, this would
break pg_upgrade'ability of databases containing line values; but
it seems unlikely that there are any (they'd have had to be compiled
with -DENABLE_LINE_TYPE).
Spotted by Andres Freund.
Diffstat (limited to 'src/backend/utils/adt/arrayutils.c')
0 files changed, 0 insertions, 0 deletions