Re: Checking return value of SPI_execute

Поиск
Список
Период
Сортировка
От Alvaro Herrera
Тема Re: Checking return value of SPI_execute
Дата
Msg-id 20191107173829.GA19178@alvherre.pgsql
обсуждение исходный текст
Ответ на Re: Checking return value of SPI_execute  (Mark Dilger <hornschnorter@gmail.com>)
Список 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 по дате отправления:

Предыдущее
От: Jesper Pedersen
Дата:
Сообщение: Re: Application name for pg_basebackup and friends
Следующее
От: Christoph Berg
Дата:
Сообщение: Re: plpythonu -> python3