public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tom Lane <[email protected]>
To: Nathan Bossart <[email protected]>
Cc: Andres Freund <[email protected]>
Cc: Xing Guo <[email protected]>
Cc: [email protected]
Subject: Re: PL/Python: Fix return in the middle of PG_TRY() block.
Date: Thu, 04 May 2023 08:39:03 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <20230504050108.GA2203557@nathanxps13>
References: <[email protected]>
	<20230113180335.GA2160040@nathanxps13>
	<CACpMh+D9jz4Lq3qieoU2NkhGASqekhDXnXX2USW4mHa+SWNQag@mail.gmail.com>
	<[email protected]>
	<[email protected]>
	<20230120190201.GC4106863@nathanxps13>
	<20230503202116.GA2110623@nathanxps13>
	<[email protected]>
	<20230503205838.GA2112379@nathanxps13>
	<20230504045413.GA2202617@nathanxps13>
	<20230504050108.GA2203557@nathanxps13>

Nathan Bossart <[email protected]> writes:
> Gah, right after I sent that, I realized we can remove one more volatile
> marker.  Sorry for the noise.

Hmm, I'm not sure why PLy_trigger_build_args's pltargs needs to
gain a "volatile" here?  LGTM otherwise.

			regards, tom lane

view thread (9+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: PL/Python: Fix return in the middle of PG_TRY() block.
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox