IMHO more information is needed, especially regarding how and when do
you change the call_status value in other parts of your code. For
example, if some other transaction is setting call_status to something
other than FINS and that transaction commits before the second UPDATE
comes out of wait,
Hi,
I develop telecommunication software and I have encountered problem
with isolation level in Postgres.
Our database receive special packets that informs about end of call,
and from time to time (it happens when such packets arrive almost in
the same time e.g 8ms difference) one call charge
On Tue, May 13, 2008 at 1:56 PM, Michal Szymanski [EMAIL PROTECTED] wrote:
I think problem is because we use default Read Commited isolation
level. In presented example value of credit should be changed only if
call_statusFINS and first transaction after modification of credit
value set
