Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 7C66E4766BC for ; Thu, 16 Jan 2003 10:39:30 -0500 (EST) Received: from mail.libertyrms.com (unknown [209.167.124.227]) by postgresql.org (Postfix) with ESMTP id 421144766BA for ; Thu, 16 Jan 2003 10:39:29 -0500 (EST) Received: from andrew by mail.libertyrms.com with local (Exim 3.22 #3 (Debian)) id 18ZC7B-0008Vq-00 for ; Thu, 16 Jan 2003 10:39:33 -0500 Date: Thu, 16 Jan 2003 10:39:33 -0500 From: Andrew Sullivan To: PgSQL Performance ML Subject: Re: schema/db design wrt performance Message-ID: <20030116103933.B32288@mail.libertyrms.com> Mail-Followup-To: Andrew Sullivan , PgSQL Performance ML References: <20030116135140.32097.qmail@web21106.mail.yahoo.com> <20030116092005.C22344@mail.libertyrms.com> <1042727678.892.31.camel@haggis> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <1042727678.892.31.camel@haggis>; from ron.l.johnson@cox.net on Thu, Jan 16, 2003 at 08:34:38AM -0600 X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200301/148 X-Sequence-Number: 795 On Thu, Jan 16, 2003 at 08:34:38AM -0600, Ron Johnson wrote: > On Thu, 2003-01-16 at 08:20, Andrew Sullivan wrote: > > 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? Yes. Remember, _both_ of these are doing SELECT. . .FOR UPDATE. Which means they both try to lock the corresponding record. But they can't _both_ lock the same record; that's what the lock prevents. A -- ---- Andrew Sullivan 204-4141 Yonge Street Liberty RMS Toronto, Ontario Canada M2P 2A8 +1 416 646 3304 x110