| From: | "A(dot)Bhuvaneswaran" <bhuvansql(at)myrealbox(dot)com> |
|---|---|
| To: | Matt Mello <alien(at)spaceship(dot)com> |
| Cc: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: "deadlock detected" documentation |
| Date: | 2003-05-07 04:58:15 |
| Message-ID: | Pine.LNX.4.44.0305071019080.1048-100000@Bhuvan.bksys.co.in |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
> I just got a "deadlock detected" SQL error from the backend. I've never
> received one of these before, but I just released new pooling code, so
> I'm concerned.
>
> Can someone point me to documentation on what this is and how to prevent
> it? [My search on the newsgroups yielded far too much for me to read.]
Deadlock occurs when two transactions try to wait for each other. In other
words, if two processes try to update two tables which have a reference to
same table, deadlock is detected. I donot know whether it is a bug or
bottle neck in postgresql. Mostly it can be avoided using locks. For
details, refer,
http://www.postgresql.org/docs/view.php?version=7.3&idoc=1&file=sql-lock.html
regards,
bhuvaneswaran
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ries van Twisk | 2003-05-07 07:34:46 | Re: UNIQUE boolean: only one row may be "true" |
| Previous Message | Tom Lane | 2003-05-07 04:46:59 | Re: "deadlock detected" documentation |