aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2012-02-08 11:29:29 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2012-02-08 11:29:29 -0500
commit3db6524fe63f0598dcb2b307bb422bc126f2b15d (patch)
treea12d229351b5da7444a4349426735fdb78352e86 /src/backend/access/gist
parentc13897983a0006e658fb7c6410d72ca59fb87136 (diff)
downloadpostgresql-3db6524fe63f0598dcb2b307bb422bc126f2b15d.tar.gz
postgresql-3db6524fe63f0598dcb2b307bb422bc126f2b15d.zip
Mark some more I/O-conversion-invoking functions as stable not volatile.
When written, textanycat, anytextcat, quote_literal, and quote_nullable were marked volatile, because they could invoke arbitrary type-specific output functions as part of casting their anyelement arguments to text. Since then, we have defined a project policy that I/O functions must not be volatile, as per commit aab353a60b95aadc00f81da0c6d99bde696c4b75. So these functions can safely be downgraded to stable. Most of the time this makes no difference since they'll get inlined anyway, but as noted by Andrew Dunstan, there are cases where the volatile marking prevents optimizations that the planner does before function inlining. (I think I might have overlooked these functions in the earlier commit on the grounds that inlining would make it moot, but not so --- tgl) This change results in a change in the expected output of the json regression tests, because the planner can now flatten a sub-select that it failed to before. The old output is preferable, but getting that back will require some as-yet-unfinished work on RowExpr handling. Marti Raudsepp
Diffstat (limited to 'src/backend/access/gist')
0 files changed, 0 insertions, 0 deletions