From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Josh Berkus" <josh(at)agliodbs(dot)com> |
Cc: | Aspire Something <aspire420(at)hotpop(dot)com>, pgsql-novice <pgsql-novice(at)postgresql(dot)org> |
Subject: | Re: Function Comit |
Date: | 2003-02-27 22:46:24 |
Message-ID: | 29886.1046385984@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
"Josh Berkus" <josh(at)agliodbs(dot)com> writes:
> However, there have been some problems with this visibility issue in
> long-running PL/pgSQL functions before. So I'd like to see if you've
> discovered a new problem; if I can reproduce it, I'll post it to BUGS.
Since these functions are all executing within the same transaction,
it's not really a transactional issue. What it could be is a question
of where CommandCounterIncrement() gets done --- that has to happen
between func2() and func3() else func2's changes won't be considered
done yet. I'd expect that to happen in most cases, but with a
sufficiently weird flow of control maybe it doesn't happen? Anyway,
let's see the test case.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Warren Massengill | 2003-02-27 22:58:46 | Re: initdb "file not found" |
Previous Message | Josh Berkus | 2003-02-27 21:44:25 | Re: Function Comit |