| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
| Cc: | "Orr, Steve" <sorr(at)rightnow(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Server error and deadlocks |
| Date: | 2003-01-14 04:18:23 |
| Message-ID: | 12874.1042517903@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> writes:
> On Mon, 13 Jan 2003, Orr, Steve wrote:
>> Finally, there are LOTS of deadlocks and I'm thinking it's because they are
>> not doing "SELECT ... FOR UPDATE" or are explictly locking tables. Or they
>> are constantly updating the same rows. It seems our duhvelopers need to get
> Well, if you're using foreign keys, you might be running into a deficiency
> in the foreign key implementation.
If these folk are immigrants from MySQL, I bet they're not using foreign
keys. Taking table-level locks seems like a more likely route to
deadlock. But this is all guesswork --- we need to see some info about
the queries being issued before we can opine about the real cause.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alex Zavalin | 2003-01-14 05:22:20 | libraries |
| Previous Message | Tom Lane | 2003-01-14 02:39:52 | Re: String functions like split() and join() in plpgsql |