From: | "Greg Sabino Mullane" <greg(at)turnstep(dot)com> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: Deferred FK / PK deletion problems |
Date: | 2007-10-15 22:11:37 |
Message-ID: | 57c7cbd7788f19bee84b9a99c465a0df@biglumber.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
Tom Lane wrote:
>> Came across an odd bug while dealing with deferred foreign keys.
> I'm not convinced this is a bug.
Can you elaborate on this? Am I doing something wrong in my app?
Someone on irc pointed out that this affects more than deferred
fk, but for my purposes, here's what's happening:
Table A has a primary key.
Table B references that primary key.
Process A periodically updates the table by doing
(basically) a delete all/insert new data, inside of
a transaction.
Process B is adding entries to table B.
If Process B happens in the "middle" of Process A,
the insert to B fails as it claims that the corresponding
row in table A does not exist.
Short of Process A grabbing an exclusive lock on the table, I
can't see a way around this. Feel free to punt this to
general if this is the expected behavior.
- --
Greg Sabino Mullane greg(at)turnstep(dot)com
PGP Key: 0x14964AC8 200710151809
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----
iD8DBQFHE+VUvJuQZxSWSsgRAzyGAKCveD8q0a8O2XFEkD1g5f08Z58mbgCgvHUF
z4bBO7MJ0gWow1fPHJY09is=
=ohAQ
-----END PGP SIGNATURE-----
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2007-10-15 22:53:51 | Re: BUG #3667: Job scheduling with Greenplum fails |
Previous Message | Dave Page | 2007-10-15 21:54:12 | Re: BUG #3667: Job scheduling with Greenplum fails |