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

From Michael Paquier
Subject Re: Checking return value of SPI_execute
Date
Msg-id 20191106042757.GE1604@paquier.xyz
Whole thread Raw
In response to Checking return value of SPI_execute  (Mark Dilger <hornschnorter@gmail.com>)
Responses Re: Checking return value of SPI_execute  (Pavel Stehule <pavel.stehule@gmail.com>)
Re: Checking return value of SPI_execute  (Mark Dilger <hornschnorter@gmail.com>)
List pgsql-hackers
On Tue, Nov 05, 2019 at 05:21:25PM -0800, Mark Dilger wrote:
> please find attached a patch fixing a problem previously discussed [1] about
> the code inappropriately ignoring the return value from SPI_execute.
>
> I will be adding this to https://commitfest.postgresql.org/26/
> shortly.

Yes, this should be fixed.

> -    SPI_execute(query, true, 0);
> +    spi_result = SPI_execute(query, true, 0);
> +    if (spi_result < 0)
> +        elog(ERROR, "SPI_execute returned %s", SPI_result_code_string(spi_result));

Any queries processed in xml.c are plain SELECT queries, so it seems
to me that you need to check after SPI_OK_SELECT as only valid
result.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [PATCH][DOC] Fix for PREPARE TRANSACTION doc and postgres_fdwmessage.
Next
From: Michael Paquier
Date:
Subject: Re: Include RELKIND_TOASTVALUE in get_relkind_objtype