mirror of
https://github.com/postgres/postgres.git
synced 2025-06-26 12:21:12 +03:00
Run pgindent on the previous commit.
Clean up after rearranging PG_TRY blocks. Author: Tom Lane <tgl@sss.pgh.pa.us> Discussion: https://postgr.es/m/2954090.1748723636@sss.pgh.pa.us Backpatch-through: 13
This commit is contained in:
@ -285,8 +285,8 @@ PLy_traceback(PyObject *e, PyObject *v, PyObject *tb,
|
||||
long plain_lineno;
|
||||
|
||||
/*
|
||||
* The second frame points at the internal function, but to mimic
|
||||
* Python error reporting we want to say <module>.
|
||||
* The second frame points at the internal function, but to
|
||||
* mimic Python error reporting we want to say <module>.
|
||||
*/
|
||||
if (*tb_depth == 1)
|
||||
fname = "<module>";
|
||||
@ -315,10 +315,10 @@ PLy_traceback(PyObject *e, PyObject *v, PyObject *tb,
|
||||
* If we know the current procedure, append the exact line
|
||||
* from the source, again mimicking Python's traceback.py
|
||||
* module behavior. We could store the already line-split
|
||||
* source to avoid splitting it every time, but producing a
|
||||
* traceback is not the most important scenario to optimize
|
||||
* for. But we do not go as far as traceback.py in reading
|
||||
* the source of imported modules.
|
||||
* source to avoid splitting it every time, but producing
|
||||
* a traceback is not the most important scenario to
|
||||
* optimize for. But we do not go as far as traceback.py
|
||||
* in reading the source of imported modules.
|
||||
*/
|
||||
line = get_source_line(exec_ctx->curr_proc->src, plain_lineno);
|
||||
if (line)
|
||||
|
Reference in New Issue
Block a user