"David G. Johnston" <david.g.johnston@gmail.com> writes: > On Saturday, August 10, 2024, Tom Lane <tgl@sss.pgh.pa.us> wrote: >> That would break a lot of code (much of it not under our control) to >> little purpose; it would also foreclose the option to return to using >> SPI_ERROR_CONNECT someday.
> I suggest we document it as deprecated and insist any future attempt to > implement a return-on-error connection function define a completely new > function.
I don't know if that usage pattern has propagated outside Postgres core, but it might've.
I'd give it decent odds since our example usage doesn't include the test.
