From: | Daniel Åkerud <zilch(at)home(dot)se> |
---|---|
To: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Lock up, but not deadlock? |
Date: | 2002-03-07 19:08:51 |
Message-ID: | 001401c1c60b$856dccb0$6400a8c0@studio |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Is there a possibility that there will be a lock in a transaction, but it is not a deadlock?
I have N functions (about 20-25) interacting in a system. They are like: setUserOnline(...) setUserOffline(...) setServerOnline(...) and so forth. We have found out that there are sometimes deadlocks. We have solved this by trying again 5 times. Most oftenly it works after the first retry, and worst case has been 2 so far. Anyway, is there a possibility that these functions (we have NO manual lock obtaining in them) cause lockups that is not called deadlocks but has to be solved anyway? Like an UPDATE waiting for another statement in another function, but it's not a circular thingy (a.k.a deadlock). Thanks for any help!
Daniel Åkerud
From | Date | Subject | |
---|---|---|---|
Next Message | Alaric B Snell | 2002-03-07 19:09:59 | Re: What are functional indices good for? |
Previous Message | Neil Conway | 2002-03-07 19:01:00 | Re: HELP!.. "semget(key=2, num=17, 03600) failed: No |