aboutsummaryrefslogtreecommitdiff
path: root/src/backend/parser/parse_utilcmd.c
diff options
context:
space:
mode:
authorPeter Eisentraut <peter_e@gmx.net>2011-04-20 23:19:04 +0300
committerPeter Eisentraut <peter_e@gmx.net>2011-04-20 23:19:04 +0300
commit395fcac29906d22615ba68bd1dfa31daf691979e (patch)
tree69bddb61cc96cab13dec15dd99516293649ac727 /src/backend/parser/parse_utilcmd.c
parent0262251c337ca066d1b1698684784254849b5676 (diff)
downloadpostgresql-395fcac29906d22615ba68bd1dfa31daf691979e.tar.gz
postgresql-395fcac29906d22615ba68bd1dfa31daf691979e.zip
Fix PL/Python traceback for error in separate file
It assumed that the lineno from the traceback always refers to the PL/Python function. If you created a PL/Python function that imports some code, runs it, and that code raises an exception, PLy_traceback would get utterly confused. Now we look at the file name reported with the traceback and only print the source line if it came from the PL/Python function. Jan UrbaƄski
Diffstat (limited to 'src/backend/parser/parse_utilcmd.c')
0 files changed, 0 insertions, 0 deletions