Skip site navigation (1) Skip section navigation (2)

Re: Signature change for SPI_cursor_open

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Thomas Hallgren <thhal(at)mailblocks(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Signature change for SPI_cursor_open
Date: 2004-10-30 19:53:39
Message-ID: 11383.1099166019@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Thomas Hallgren <thhal(at)mailblocks(dot)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

In response to

pgsql-hackers by date

Next:From: David FetterDate: 2004-10-30 19:54:40
Subject: array_to_column function
Previous:From: Thomas HallgrenDate: 2004-10-30 19:20:34
Subject: Re: Signature change for SPI_cursor_open

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group