From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Mark Dilger <hornschnorter@gmail.com>
Cc: Pavel Stehule <pavel.stehule@gmail.com>
Cc: Michael Paquier <michael@paquier.xyz>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: Checking return value of SPI_execute
Date: Thu, 7 Nov 2019 14:38:29 -0300
Message-ID: <20191107173829.GA19178@alvherre.pgsql> (raw)
In-Reply-To: <1de13b09-a5a0-4c6e-0470-5ecebc0a7784@gmail.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: alvherre@2ndquadrant.com, hornschnorter@gmail.com, pavel.stehule@gmail.com, michael@paquier.xyz
Subject: Re: Checking return value of SPI_execute
In-Reply-To: <20191107173829.GA19178@alvherre.pgsql>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox