Re: Signature change for SPI_cursor_open - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Signature change for SPI_cursor_open
Date
Msg-id 11383.1099166019@sss.pgh.pa.us
Whole thread Raw
In response to Signature change for SPI_cursor_open  (Thomas Hallgren <thhal@mailblocks.com>)
List pgsql-hackers
Thomas Hallgren <thhal@mailblocks.com> writes:
> Ok, now I understand. Thanks for the explanation. I guess that if 
> read_only is set to true and an attempt is made to execute a plan that 
> has side effect, that will cause an ERROR?

Right, it'll bounce anything except a SELECT query.  (This test is not
watertight; consider SELECT nextval() ... but on the other hand that's a
non-transactional operation that does not care about snapshots anyway.)
        regards, tom lane


pgsql-hackers by date:

Previous
From: Thomas Hallgren
Date:
Subject: Re: Signature change for SPI_cursor_open
Next
From: David Fetter
Date:
Subject: array_to_column function