pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ron Johnson <ron.l.johnson@cox.net>
To: PgSQL Performance ML <pgsql-performance@postgresql.org>
Subject: Re: schema/db design wrt performance
Date: 16 Jan 2003 08:34:38 -0600
Message-ID: <1042727678.892.31.camel@haggis> (raw)
In-Reply-To: <20030116092005.C22344@mail.libertyrms.com>
References: <20030116135140.32097.qmail@web21106.mail.yahoo.com>
	<20030116092005.C22344@mail.libertyrms.com>

On Thu, 2003-01-16 at 08:20, Andrew Sullivan wrote:
> On Thu, Jan 16, 2003 at 05:51:40AM -0800, CaptainX0r wrote:
> > All,
> > 
> > I just noted in another thread that use of foreign keys in postgres
> > significantly hinders performance.  I'm wondering what other
> 
> Since I think I'm the one responsible for this, I'd better say
> something clearer for the record.
> 
> The foreign keys implementation in PostgreSQL essentially uses SELECT
> . . . FOR UPDATE to ensure that referenced data doesn't go away while a
> referencing datum is being inserted or altered.
> 
> The problem with this is that frequently-referenced data are
> therefore effectively locked during the operation.  Other writers
> will block on the locked data until the first writer finishes.
> 
> So, for instance, consider two artificial-example tables:
> 
> create table account (acct_id serial primary key);
> 
> create table acct_activity (acct_id int references
> account(acct_id), trans_on timestamp, val numeric(12,2));
> 
> If a user has multiple connections and charges things to the same
> account in more than one connection at the same time, the
> transactions will have to be processed, effectively, in series: each
> one will have to wait for another to commit in order to complete.

This is true even though the default transaction mode is
READ COMMITTED?

-- 
+------------------------------------------------------------+
| Ron Johnson, Jr.     mailto:ron.l.johnson@cox.net          |
| Jefferson, LA  USA   http://members.cox.net/ron.l.johnson  |
|                                                            |
| "Basically, I got on the plane with a bomb. Basically, I   |
|  tried to ignite it. Basically, yeah, I intended to damage |
|  the plane."                                               |
|    RICHARD REID, who tried to blow up American Airlines    |
|                  Flight 63                                 |
+------------------------------------------------------------+




view thread (12+ messages)  latest in thread

Message-ID: <1042727678.892.31.camel@haggis>
Permalink:  ../1042727678.892.31.camel@haggis/
Also on:    postgresql.org/message-id/1042727678.892.31.camel@haggis

 · 

reply

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: ron.l.johnson@cox.net
  Subject: Re: schema/db design wrt performance
  In-Reply-To: <1042727678.892.31.camel@haggis>
  References: <20030116135140.32097.qmail@web21106.mail.yahoo.com> <20030116092005.C22344@mail.libertyrms.com> <1042727678.892.31.camel@haggis>

* 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