From: | Andrew Sullivan <andrew(at)libertyrms(dot)info> |
---|---|
To: | PgSQL Performance ML <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: schema/db design wrt performance |
Date: | 2003-01-16 15:39:33 |
Message-ID: | 20030116103933.B32288@mail.libertyrms.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
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
<andrew(at)libertyrms(dot)info> M2P 2A8
+1 416 646 3304 x110
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-01-16 15:46:22 | Re: 7.3.1 New install, large queries are slow |
Previous Message | Tom Lane | 2003-01-16 15:13:37 | Re: 7.3.1 New install, large queries are slow |