RE: The return value of SPI_connect - Mailing list pgsql-hackers

From Hou, Zhijie
Subject RE: The return value of SPI_connect
Date
Msg-id f8d9302593874cb3b5bd31005735715d@G08CNEXMBPEKD05.g08.fujitsu.local
Whole thread Raw
In response to Re: The return value of SPI_connect  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> > May be we can make "int SPI_connect()" => "void SPI_connect()" and fix
> the doc ?
>
> I don't see a lot of value in changing SPI_connect() in isolation.
> It's part of an API suite that generally expects functions to return error
> codes.
>
> There was a previous thread [1] about getting rid of useless SPI error codes
> across the board, in favor of having those functions throw errors for error
> cases.  AFAICT nobody has reviewed the proposed patch there, but maybe you'd
> like to?
>
>             regards, tom lane
>
> [1]
> https://www.postgresql.org/message-id/flat/cc57ea5c-592a-6c27-aca6-7ad
> 2a166c379%40gmail.com
>
Thanks ! I will look into it.

Best regards,
houzj






pgsql-hackers by date:

Previous
From: Andy Fan
Date:
Subject: Re: BLOB / CLOB support in PostgreSQL
Next
From: Tom Lane
Date:
Subject: Re: Small improvements to pg_list.h's linitial(), lsecond(), lthird() etc macros