| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
| Cc: | Philippe Lang <philippe(dot)lang(at)attiksystem(dot)ch>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: FKs and deadlocks |
| Date: | 2004-10-22 14:14:35 |
| Message-ID: | 6576.1098454475@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> writes:
> On Fri, 22 Oct 2004, Philippe Lang wrote:
>> I don't know if anyone has a better idea, but I would like to try taking
>> away some FKs in my schema. My problem is that I really don't know which
>> one to delete. There are over 40 tables. Are there rules to do that? Or
>> maybe can I simply wait on the next deadlock, and try understanding who
>> got locked by who? OK, but how can I do that?
> I think you may be able to do this if you turn on statement locking and
> try to resurrect the state from the logs.
Also look in pg_locks and pg_activity.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-10-22 14:18:06 | Re: Row versioning |
| Previous Message | Davide Negri | 2004-10-22 13:52:36 | Log |