erm, you're right (re-tested that today)
I don't know what happened the other day. The query updating the flag
would not return until the test function was done.
I must have made the test duration too short, so that it was only appearances.
whatever, it works. thanks.
WBL
On Wed, Jul 6, 2011 at
I'd like to do a dirty read from plpgsql, so that i can stop the function
that is in a long loop without rolling back the work that it did.
All i want to read is a flag that says 'stop'.
I've figured 2 ways of doing that, both of which i don't like very much.
* with a sequence: while value =
On 6/07/2011 6:54 PM, Willy-Bas Loos wrote:
I'd like to do a dirty read from plpgsql, so that i can stop the
function that is in a long loop without rolling back the work that it
did.
All i want to read is a flag that says 'stop'.
I've figured 2 ways of doing that, both of which i don't like
On Wed, Jul 06, 2011 at 12:54:21PM +0200, Willy-Bas Loos wrote:
I'd like to do a dirty read from plpgsql, so that i can stop the function
that is in a long loop without rolling back the work that it did.
All i want to read is a flag that says 'stop'.
this doesn't need dirty read.
just read
