database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-06-26 12:21:12 +03:00
Code Activity

Run pgindent on the previous commit.

Browse Source 
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:
Tom Lane
2025-06-01 14:55:24 -04:00
parent b56a92651a
commit b898bb2a79
1 changed files with 129 additions and 129 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
src/pl/plpython/plpy_elog.c
View File

@ -285,8 +285,8 @@ PLy_traceback(PyObject *e, PyObject *v, PyObject *tb,
long plain_lineno; long plain_lineno;
/* /*
* The second frame points at the internal function, but to mimic * The second frame points at the internal function, but to
* Python error reporting we want to say <module>. * mimic Python error reporting we want to say <module>.
*/ */
if (*tb_depth == 1) if (*tb_depth == 1)
fname = "<module>"; fname = "<module>";
@ -315,10 +315,10 @@ PLy_traceback(PyObject *e, PyObject *v, PyObject *tb,
* If we know the current procedure, append the exact line * If we know the current procedure, append the exact line
* from the source, again mimicking Python's traceback.py * from the source, again mimicking Python's traceback.py
* module behavior. We could store the already line-split * module behavior. We could store the already line-split
* source to avoid splitting it every time, but producing a * source to avoid splitting it every time, but producing
* traceback is not the most important scenario to optimize * a traceback is not the most important scenario to
* for. But we do not go as far as traceback.py in reading * optimize for. But we do not go as far as traceback.py
* the source of imported modules. * in reading the source of imported modules.
*/ */
line = get_source_line(exec_ctx->curr_proc->src, plain_lineno); line = get_source_line(exec_ctx->curr_proc->src, plain_lineno);
if (line) if (line)