| From: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
|---|---|
| To: | "Orr, Steve" <sorr(at)rightnow(dot)com> |
| Cc: | "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Server error and deadlocks |
| Date: | 2003-01-14 17:35:07 |
| Message-ID: | Pine.LNX.4.33.0301141033580.14416-100000@css120.ihs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Johnson, Shaunn | 2003-01-14 17:45:57 | intro to DBA classes |
| Previous Message | Thomas Beutin | 2003-01-14 17:07:13 | Re: time to restore a database |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ross J. Reedstrom | 2003-01-14 17:43:45 | Re: copying perms to another user |
| Previous Message | Peter Eisentraut | 2003-01-14 17:15:41 | Re: copying perms to another user |