X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 5FB35D1B45E for ; Mon, 5 Jan 2004 18:39:28 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 36668-05 for ; Mon, 5 Jan 2004 14:38:38 -0400 (AST) Received: from wolff.to (wolff.to [66.93.249.74]) by svr1.postgresql.org (Postfix) with SMTP id C8525D1B44E for ; Mon, 5 Jan 2004 14:38:37 -0400 (AST) Received: (qmail 11079 invoked by uid 500); 5 Jan 2004 18:38:59 -0000 Date: Mon, 5 Jan 2004 12:38:59 -0600 From: Bruno Wolff III To: Vivek Khera Cc: pgsql-performance@postgresql.org Subject: Re: deferred foreign keys Message-ID: <20040105183859.GA28448@wolff.to> Mail-Followup-To: Vivek Khera , pgsql-performance@postgresql.org References: <3FF4FA25.7050802@familyhealth.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.4i X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/39 X-Sequence-Number: 5214 On Mon, Jan 05, 2004 at 11:33:40 -0500, Vivek Khera wrote: > > Thanks. Then it sorta makes it moot for me to try deferred checks, > since the Pimary and Foreign keys never change once set. I wonder > what is making the transactions appear to run lockstep, then... I think this is probably the issue with foreign key checks needing an exclusive lock, since there is no shared lock that will prevent deletes. This problem has been discussed a number of times on the lists and you should be able to find out more information from the archives if you want to confirm that this is the root cause of your problems.