Re: pgsql: Add optional parameter to PG_TRY() macros

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Add optional parameter to PG_TRY() macros
Date: 2026-11-10 21:45:42
Message-ID: CAApHDvrCOdLJbGc8MJdzmD3V_H7U+8X9JcXOkwLg7WRrkxzG_A@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Wed, 11 Nov 2026 at 10:12, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Add optional parameter to PG_TRY() macros

There's no public discussion about it, and I didn't think it critical
enough to open a new thread about. I believe the newly added
PG_PERL_TRY() macros would need a ##__VA_ARGS__ suffix on all the
local variables, else we'd get shadow warnings if we ever nested
PG_PERL_TRYs.

David

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2026-11-10 22:14:01 Re: pgsql: Add optional parameter to PG_TRY() macros
Previous Message Tom Lane 2026-11-10 21:33:04 pgsql: Fix missing error handling in plperl_sv_to_literal().