Re: [plpython] Add missing volatile qualifier.
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Nathan Bossart <nathandbossart@gmail.com>
Cc: Xing Guo <higuoxing@gmail.com>,
pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2024-04-01T18:39:05Z
Lists: pgsql-hackers
Nathan Bossart <nathandbossart@gmail.com> writes: > On Mon, Apr 01, 2024 at 11:57:07AM -0400, Tom Lane wrote: >> Good catch! It looks like the consequences of a failure would be >> pretty minimal --- AFAICS, no worse than a possible failure to remove >> a refcount on Py_None --- but that's still a bug. > Huh. I seem to have dropped that "volatile" shortly before committing for > some reason [0]. Oh, I'd forgotten that discussion. Given that we were both confused about the need for it, all the more reason to try to avoid using a within-PG_TRY assignment. > Your fix seems fine to me. Thanks for looking, I'll push it shortly. regards, tom lane
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Avoid possible longjmp-induced logic error in PLy_trigger_build_args.
- fb60118bf233 13.15 landed
- d96f72569743 14.12 landed
- 5eac8cef2454 17.0 landed
- 30fe8a7ba07e 12.19 landed
- 14e4e8f8c66b 16.3 landed
- 08bdf0a4798b 15.7 landed