| From: | Thomas Hallgren <thhal(at)mailblocks(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Signature change for SPI_cursor_open |
| Date: | 2004-10-30 19:20:34 |
| Message-ID: | thhal-0BYJfAr/W3kAWrQhCjD4kA228g9TPwB@mailblocks.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> You should set the flag if and only if you are executing a pl/java
> function that has a provolatile setting of "stable" or "immutable".
> The new rule is that only functions declared "volatile" are allowed
> to have side effects on the database. See pghackers discussions in
> early September about updating snapshots, doing CommandCounterIncrement,
> and so forth within functions.
>
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?
Regards,
Thomas Hallgren
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-10-30 19:53:39 | Re: Signature change for SPI_cursor_open |
| Previous Message | Alvaro Herrera | 2004-10-30 19:07:30 | Re: 8.0b4: COMMIT outside of a transaction echoes ROLLBACK |