Re: Making pgfdw_report_error statically analyzable

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Álvaro Herrera <alvherre(at)kurilemu(dot)de>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Making pgfdw_report_error statically analyzable
Date: 2025-07-29 14:37:41
Message-ID: 982683.1753799861@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I wrote:
> I'll run with Alvaro's suggestion, then.

And done. In the event I realized that there's no point in
back-patching this, because 80aa9848b already changed all
the call sites of pgfdw_report_error, so we're already going
to have issues back-patching any fixes that touch those.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2025-07-29 15:27:37 Re: Regression with large XML data input
Previous Message Bruce Momjian 2025-07-29 14:19:13 Re: Doc update proposal for the note on log_statement in the runtime config for logging page