| From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
|---|---|
| To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
| Cc: | Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: deadlock problem |
| Date: | 2003-03-31 16:41:59 |
| Message-ID: | 20030331084135.O35743-100000@megazone23.bigpanda.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, 31 Mar 2003, Christopher Kings-Lynne wrote:
> I'm always getting deadlocks like this:
>
> [30-Mar-2003 19:19:51] PHP Fatal error: postgres7 error: [0: ERROR:
> deadlock detected
> ] in EXECUTE("INSERT INTO users_foods (user_id, date, meal_id, quantity,
> eaten, food_id) VALUES ('55283', '2003-04-07', '1', '1.00', 'f', '779')")
> in /usr/local/www/generic/lib/adodb/adodb-errorhandler.inc.php on line 71
>
>
> Why would an INSERT cause a deadlock problem? Is this due to the FOR UPDATE
> problem with foreign keys?
Probably if this table is on either side of one.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2003-03-31 16:43:29 | Re: updateable cursors & visibility |
| Previous Message | Bruce Momjian | 2003-03-31 16:39:46 | Re: deadlock problem |