diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2024-04-01 15:15:03 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2024-04-01 15:15:03 -0400 |
| commit | 08bdf0a4798bbbbc401bd951cd9553f3c6de2de7 (patch) | |
| tree | 91cea91abd104b0d2f49495254f07fadcddd92e3 /contrib/postgres_fdw/postgres_fdw.c | |
| parent | 03561a6c7bbfe305b941d46f7bafb3cdd4793982 (diff) | |
| download | postgresql-08bdf0a4798bbbbc401bd951cd9553f3c6de2de7.tar.gz postgresql-08bdf0a4798bbbbc401bd951cd9553f3c6de2de7.zip | |
Avoid possible longjmp-induced logic error in PLy_trigger_build_args.
The "pltargs" variable wasn't marked volatile, which makes it unsafe
to change its value within the PG_TRY block. It looks like the worst
outcome would be to fail to release a refcount on Py_None during an
(improbable) error exit, which would likely go unnoticed in the field.
Still, it's a bug. A one-liner fix could be to mark pltargs volatile,
but on the whole it seems cleaner to arrange things so that we don't
change its value within PG_TRY.
Per report from Xing Guo. This has been there for quite awhile,
so back-patch to all supported branches.
Discussion: https://postgr.es/m/CACpMh+DLrk=fDv07MNpBT4J413fDAm+gmMXgi8cjPONE+jvzuw@mail.gmail.com
Diffstat (limited to 'contrib/postgres_fdw/postgres_fdw.c')
0 files changed, 0 insertions, 0 deletions