Re: SPI_connect, SPI_connect_ext return type

From: Stepan Neretin <sndcppg(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: SPI_connect, SPI_connect_ext return type
Date: 2024-09-08 06:35:00
Message-ID: CAMaYL5Z8iQea4oonLywEEifB1EzegMabpS0_fMjNz4cOA=7qig@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> So if we tell extension authors they don't need to check the result, it's
unlikely
> that that will cause any new code they write to get used with PG
> versions where it would be wrong.
Yes, I concur.

> This combines portions of Stepan's
> two patches with some additional work (mostly, that he'd missed fixing
> any of contrib/).
Thank you for the feedback! I believe the patch looks satisfactory. Should
we await a review? The changes seem straightforward to me.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2024-09-08 07:31:23 Re: SPI_connect, SPI_connect_ext return type
Previous Message 清浅 2024-09-08 05:01:37 Fix orphaned 2pc file which may casue instance restart failed