aboutsummaryrefslogtreecommitdiff
path: root/contrib/intarray/_int_gist.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2007-02-06 17:35:34 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2007-02-06 17:35:34 +0000
commitc60125a9be51f98cdcda8de264f5bccf106788d8 (patch)
treee4cffa95b7395167d1aefbb79c04b8f7508047df /contrib/intarray/_int_gist.c
parent7fd912e854b502a787de1830085dfbae6043b0d0 (diff)
downloadpostgresql-c60125a9be51f98cdcda8de264f5bccf106788d8.tar.gz
postgresql-c60125a9be51f98cdcda8de264f5bccf106788d8.zip
Remove typmod checking from the recent security-related patches. It turns
out that ExecEvalVar and friends don't necessarily have access to a tuple descriptor with correct typmod: it definitely can contain -1, and possibly might contain other values that are different from the Var's value. Arguably this should be cleaned up someday, but it's not a simple change, and in any case typmod discrepancies don't pose a security hazard. Per reports from numerous people :-( I'm not entirely sure whether the failure can occur in 8.0 --- the simple test cases reported so far don't trigger it there. But back-patch the change all the way anyway.
Diffstat (limited to 'contrib/intarray/_int_gist.c')
0 files changed, 0 insertions, 0 deletions