> 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
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
