Horton

Re: Making pgfdw_report_error statically analyzable

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Álvaro Herrera <alvherre@kurilemu.de>, pgsql-hackers@lists.postgresql.org
Date: 2025-07-29T14:37:41Z
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

Commits

  1. Split up pgfdw_report_error so that we can mark it pg_noreturn.