Re: Server error and deadlocks - Mailing list pgsql-general

From scott.marlowe
Subject Re: Server error and deadlocks
Date
Msg-id Pine.LNX.4.33.0301141033580.14416-100000@css120.ihs.com
Whole thread Raw
In response to Re: Server error and deadlocks  ("Orr, Steve" <sorr@rightnow.com>)
List pgsql-general
On Tue, 14 Jan 2003, Orr, Steve wrote:

> You're right about the lack of foreign keys... it's a foreign concept to the
> DUHvelopers. I suspect table locks but are there any database level tracing
> tools to show the SQL? Will the trace_locks and debug_deadlocks parameters
> help and how do I use them?

Actually, what you need is a code audit and some training for your
developers on how real transactions work and why they don't need to use
table level locks.

I'd have them study and learn from the section in the manual on MVCC and
then go back in and change their code to use transactions with select for
update instead of table locks.


pgsql-general by date:

Previous
From: Lincoln Yeoh
Date:
Subject: Re: time to restore a database
Next
From: "Johnson, Shaunn"
Date:
Subject: intro to DBA classes