Re: Checking return value of SPI_execute - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Checking return value of SPI_execute
Date
Msg-id 20191107173829.GA19178@alvherre.pgsql
Whole thread Raw
In response to Re: Checking return value of SPI_execute  (Mark Dilger <hornschnorter@gmail.com>)
List pgsql-hackers
On 2019-Nov-07, Mark Dilger wrote:

> I'd like to keep the status codes for (a) but deprecate error codes for (b)
> in favor of elog(ERROR).  I don't see that these elogs should ever be a
> problem, since getting one in testing would indicate the need to fix bad C
> code, not the need to catch an exception and take remedial action at run
> time.  Does this adequately address your concern?

Yes, I think it does.


-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Jesper Pedersen
Date:
Subject: Re: Application name for pg_basebackup and friends
Next
From: Christoph Berg
Date:
Subject: Re: plpythonu -> python3