|
Re: Function Comit: msg#00294db.postgresql.novice
"Josh Berkus" <josh@xxxxxxxxxxxx> 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 ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: Function Comit: 00294, Josh Berkus |
|---|---|
| Next by Date: | Re: initdb "file not found": 00294, Warren Massengill |
| Previous by Thread: | Re: Function Comiti: 00294, Josh Berkus |
| Next by Thread: | initdb hangs even though ipc-daemon is running?: 00294, Tom Gilbert |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |