aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeBitmapIndexscan.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2017-03-07 12:40:44 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2017-03-07 12:40:44 -0500
commit0d2b1f305dc78d536d80cfb4bb2ac4d7104453db (patch)
tree9533fac7832e9b7d5da31ac9f67cda972a584689 /src/backend/executor/nodeBitmapIndexscan.c
parent03cf2219346aa78ecd1b6d4501a7697692a43c62 (diff)
downloadpostgresql-0d2b1f305dc78d536d80cfb4bb2ac4d7104453db.tar.gz
postgresql-0d2b1f305dc78d536d80cfb4bb2ac4d7104453db.zip
Invent start_proc parameters for PL/Tcl.
Define GUCs pltcl.start_proc and pltclu.start_proc. When set to a nonempty value at the time a new Tcl interpreter is created, the parameterless pltcl or pltclu function named by the GUC is called to allow user-controlled initialization to occur within the interpreter. This is modeled on plv8's start_proc parameter, and also has much in common with plperl's on_init feature. It allows users to fully replace the "modules" feature that was removed in commit 817f2a586. Since an initializer function could subvert later Tcl code in nearly arbitrary ways, mark both GUCs as SUSET for now. It would be nice to find a way to relax that someday; but the corresponding GUCs in plperl are also SUSET, and there's not been much complaint. Discussion: https://postgr.es/m/22067.1488046447@sss.pgh.pa.us
Diffstat (limited to 'src/backend/executor/nodeBitmapIndexscan.c')
0 files changed, 0 insertions, 0 deletions