| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Mark Dilger <hornschnorter(at)gmail(dot)com> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Checking return value of SPI_execute |
| Date: | 2019-11-07 17:38:29 |
| Message-ID: | 20191107173829.GA19178@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christoph Berg | 2019-11-07 17:38:53 | Re: plpythonu -> python3 |
| Previous Message | Jesper Pedersen | 2019-11-07 17:36:42 | Re: Application name for pg_basebackup and friends |