-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 > The DELETE returns 0 rows (and thus is the problem) according to the script.
> I've had this problem before when there is a BEFORE DELETE trigger > that is inadvertently preventing the deletion, though this seems hard > to rationalize with the rest of what you're seeing... still, any > triggers or rules on these tables? There is a trigger on both sides that does an insert to another table, but it should not prevent the deletion. Further, this session is running 'replica' mode. Going to do some more debugging this morning... - -- Greg Sabino Mullane g...@turnstep.com End Point Corporation PGP Key: 0x14964AC8 200910160720 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iEYEAREDAAYFAkrYVxYACgkQvJuQZxSWSsh8pgCdGtYA1tzFxeaq+Uwdij/BEsKf recAmweTdVFQsZc19qqu8wJNfSjvTU2+ =eLya -----END PGP SIGNATURE----- -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
