aboutsummaryrefslogtreecommitdiff
path: root/doc/FAQ_AIX
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2007-02-06 17:35:27 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2007-02-06 17:35:27 +0000
commit8d24b8bd7a0fe50b40018f2d26352184467fb68f (patch)
tree668663c0914e828339da8670f1ca7946c57f2edb /doc/FAQ_AIX
parent33623b51b685ee8dfc92e074340ce6df43e2b851 (diff)
downloadpostgresql-8d24b8bd7a0fe50b40018f2d26352184467fb68f.tar.gz
postgresql-8d24b8bd7a0fe50b40018f2d26352184467fb68f.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 'doc/FAQ_AIX')
0 files changed, 0 insertions, 0 deletions