From: Andrew Sullivan <andrew@libertyrms.info>
To: PgSQL Performance ML <pgsql-performance@postgresql.org>
Subject: Re: schema/db design wrt performance
Date: Thu, 16 Jan 2003 11:05:22 -0500
Message-ID: <20030116110522.F32288@mail.libertyrms.com> (raw)
In-Reply-To: <1042732204.892.35.camel@haggis>
References: <20030116135140.32097.qmail@web21106.mail.yahoo.com>
<20030116092005.C22344@mail.libertyrms.com>
<1042727678.892.31.camel@haggis>
<20030116103933.B32288@mail.libertyrms.com>
<1042732204.892.35.camel@haggis>
On Thu, Jan 16, 2003 at 09:50:04AM -0600, Ron Johnson wrote:
>
> Could BEFORE INSERT|UPDATE|DELETE triggers perform the same
> functionality while touching only the desired records, thus
> decreasing conflict?
You can make the constraint DEFERRABLE INITIALY DEFERRED. It helps
somewhat. But the potential for deadlock, and the backing up, will
still happen to some degree. It's a well-known flaw in the FK
system. I beleive the FK implementation was mostly intended as a
proof of concept.
A
--
----
Andrew Sullivan 204-4141 Yonge Street
Liberty RMS Toronto, Ontario Canada
<andrew@libertyrms.info> M2P 2A8
+1 416 646 3304 x110
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: andrew@libertyrms.info
Subject: Re: schema/db design wrt performance
In-Reply-To: <20030116110522.F32288@mail.libertyrms.com>
References: <20030116135140.32097.qmail@web21106.mail.yahoo.com> <20030116092005.C22344@mail.libertyrms.com> <1042727678.892.31.camel@haggis> <20030116103933.B32288@mail.libertyrms.com> <1042732204.892.35.camel@haggis> <20030116110522.F32288@mail.libertyrms.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