aboutsummaryrefslogtreecommitdiff
path: root/src/backend/parser/parse_utilcmd.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2009-11-13 22:43:42 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2009-11-13 22:43:42 +0000
commit631760998626e8fcc9d9d1ac6e7a2a5c5153b575 (patch)
treefc94e4360b89cade3895a95a5bccc21d30d86588 /src/backend/parser/parse_utilcmd.c
parent01038d4ad77eec8cdf16a39c69fc902bf30c4072 (diff)
downloadpostgresql-631760998626e8fcc9d9d1ac6e7a2a5c5153b575.tar.gz
postgresql-631760998626e8fcc9d9d1ac6e7a2a5c5153b575.zip
Add control knobs for plpgsql's variable resolution behavior, and make the
default be "throw error on conflict", as per discussions. The GUC variable is plpgsql.variable_conflict, with values "error", "use_variable", "use_column". The behavior can also be specified per-function by inserting one of #variable_conflict error #variable_conflict use_variable #variable_conflict use_column at the start of the function body. The 8.5 release notes will need to mention using "use_variable" to retain backward-compatible behavior, although we should encourage people to migrate to the much less mistake-prone "error" setting. Update the plpgsql documentation to match this and other recent changes.
Diffstat (limited to 'src/backend/parser/parse_utilcmd.c')
0 files changed, 0 insertions, 0 deletions