Re: How do BEGIN/COMMIT/ABORT operate in a nested SPI query?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: david(at)andl(dot)org
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: How do BEGIN/COMMIT/ABORT operate in a nested SPI query?
Date: 2016-04-20 14:28:33
Message-ID: 7687.1461162513@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

<david(at)andl(dot)org> writes:
> From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
>> Define "executes". You could shove those lines in via the wire protocol,
>> sure, but SPI won't take them.

> Now you really have me puzzled. What I provided is an extract from the log
> of generated SQL commands sent to the SPI interface. [Obviously there also
> values bound to the parameters which do not show up here.]

> The code executes without error and produces exactly the output I expected.

Are you remembering to check the result code from SPI_execute_whatever?

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Alex Ignatov 2016-04-20 15:05:19 Re: Initdb --data-checksums by default
Previous Message Moreno Andreo 2016-04-20 14:28:21 Re: PG 9.1 on windows setup problem