From: Stephan Szabo <sszabo@megazone.bigpanda.com>
To: Bruno Wolff III <bruno@wolff.to>
Cc: Vivek Khera <khera@kcilink.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: deferred foreign keys
Date: Mon, 5 Jan 2004 10:57:02 -0800 (PST)
Message-ID: <20040105105401.C72490@megazone.bigpanda.com> (raw)
In-Reply-To: <20040105183859.GA28448@wolff.to>
References: <x7brpruzwq.fsf@yertle.int.kciLink.com>
<x73cb0c3ep.fsf@yertle.int.kciLink.com>
<3FF4FA25.7050802@familyhealth.com.au>
<x7isjqcq3f.fsf@yertle.int.kciLink.com>
<20040105183859.GA28448@wolff.to>
On Mon, 5 Jan 2004, Bruno Wolff III wrote:
> On Mon, Jan 05, 2004 at 11:33:40 -0500,
> Vivek Khera <khera@kcilink.com> 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.
But, if he's updating the fk table but not the keyed column, it should no
longer be doing the check and grabbing the locks. If he's seeing it grab
the row locks still a full test case would be handy because it'd probably
mean we missed something.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: sszabo@megazone.bigpanda.com, bruno@wolff.to, khera@kcilink.com
Subject: Re: deferred foreign keys
In-Reply-To: <20040105105401.C72490@megazone.bigpanda.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox