aboutsummaryrefslogtreecommitdiff
path: root/src/backend/commands/trigger.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2015-08-21 20:17:19 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2015-08-21 20:17:19 -0400
commitfcdfce6820373422bcdb5630f9eb63df14fd0764 (patch)
treebd95391239fe0156fde6886309486ee44cf7c649 /src/backend/commands/trigger.c
parent072710dff3eef4540f1c64d07890eb128535e212 (diff)
downloadpostgresql-fcdfce6820373422bcdb5630f9eb63df14fd0764.tar.gz
postgresql-fcdfce6820373422bcdb5630f9eb63df14fd0764.zip
Detect mismatched CONTINUE and EXIT statements at plpgsql compile time.
With a bit of tweaking of the compile namestack data structure, we can verify at compile time whether a CONTINUE or EXIT is legal. This is surely better than leaving it to runtime, both because earlier is better and because we can issue a proper error pointer. Also, we can get rid of the ad-hoc old way of detecting the problem, which only took care of CONTINUE not EXIT. Jim Nasby, adjusted a bit by me
Diffstat (limited to 'src/backend/commands/trigger.c')
0 files changed, 0 insertions, 0 deletions