Around 19:13 on Feb 25, 2002, Tom Lane said:
# When you insert a new row into a table that has RI references, the
# referenced rows in the other table are locked down with SELECT FOR
# UPDATE locks (to ensure they won't be deleted before your own
# transaction can commit). I am not sure that this could explain your
# deadlock, but it seems like the first place to look.
It sounds like it'd be in my best interest to drop the RI for the
log, it's not terribly important in my application and would probably be
better than ``on delete set null.''
I'll give that a shot. Is there an easy way to drop the
constraint on this table, and perhaps a way to detect the constraint
programmatically? I try to keep migration kits that manage database
changes as I go for the millions of people I imagine are using my
application (imagination makes for better applications).
--
SPY My girlfriend asked me which one I like better.
pub 1024/3CAE01D5 1994/11/03 Dustin Sallings <dustin@spy.net>
| Key fingerprint = 87 02 57 08 02 D0 DA D6 C8 0F 3E 65 51 98 D8 BE
L_______________________ I hope the answer won't upset her. ____________
