aboutsummaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2010-04-14 23:52:10 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2010-04-14 23:52:10 +0000
commitf7c5ff3d6d003a33fb12d77cc4057af6e8279c84 (patch)
treeb0de885b2e5361bf4e2d66cf3e96b789afceaec1 /doc/src
parent73981cb4512a57adcb2f90a9c3cebf5ab13cf0fe (diff)
downloadpostgresql-f7c5ff3d6d003a33fb12d77cc4057af6e8279c84.tar.gz
postgresql-f7c5ff3d6d003a33fb12d77cc4057af6e8279c84.zip
Fix plpgsql's exec_eval_expr() to ensure it returns a sane type OID
even when the expression is a query that returns no rows. So far as I can tell, the only caller that actually fails when a garbage OID is returned is exec_stmt_case(), which is new in 8.4 --- in all other cases, we might make a useless trip through casting logic, but we won't fail since the isnull flag will be set. Hence, backpatch only to 8.4, just in case there are apps out there that aren't expecting an error to be thrown if the query returns more or less than one column. (Which seems unlikely, since the error would be thrown if the query ever did return a row; but it's possible there's some never-exercised code out there.) Per report from Mario Splivalo.
Diffstat (limited to 'doc/src')
0 files changed, 0 insertions, 0 deletions