Tom Lane 08bdf0a479 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		2024-04-01 15:15:03 -04:00
..
plperl	Hide warnings from Python headers when using gcc-compatible compiler.	2023-12-26 16:16:29 -05:00
plpgsql	Translation updates	2024-02-05 14:47:58 +01:00
plpython	Avoid possible longjmp-induced logic error in PLy_trigger_build_args.	2024-04-01 15:15:03 -04:00
tcl	Translation updates	2023-11-06 13:16:22 +01:00
Makefile	Make distprep and *clean build targets recurse into all subdirectories.	2011-07-03 13:55:12 -04:00