diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2014-01-08 20:18:10 -0500 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2014-01-08 20:18:10 -0500 |
commit | 47ac4473ac018f1ec5af5efb2d202646169232eb (patch) | |
tree | 9cab8ada5417d4ff7cbc5f6cbb18de0d2bd82c8d /src/backend/access/transam/xlog.c | |
parent | 3aefff422a9b0fffa7e3a6affdbf491a20c3abaa (diff) | |
download | postgresql-47ac4473ac018f1ec5af5efb2d202646169232eb.tar.gz postgresql-47ac4473ac018f1ec5af5efb2d202646169232eb.zip |
Fix "cannot accept a set" error when only some arms of a CASE return a set.
In commit c1352052ef1d4eeb2eb1d822a207ddc2d106cb13, I implemented an
optimization that assumed that a function's argument expressions would
either always return a set (ie multiple rows), or always not. This is
wrong however: we allow CASE expressions in which some arms return a set
of some type and others just return a scalar of that type. There may be
other examples as well. To fix, replace the run-time test of whether an
argument returned a set with a static precheck (expression_returns_set).
This adds a little bit of query startup overhead, but it seems barely
measurable.
Per bug #8228 from David Johnston. This has been broken since 8.0,
so patch all supported branches.
Diffstat (limited to 'src/backend/access/transam/xlog.c')
0 files changed, 0 insertions, 0 deletions