Re: schema/db design wrt performance
| От | Andrew Sullivan |
|---|---|
| Тема | Re: schema/db design wrt performance |
| Дата | |
| Msg-id | 20030116103933.B32288@mail.libertyrms.com обсуждение исходный текст |
| Ответ на | Re: schema/db design wrt performance (Ron Johnson <ron.l.johnson@cox.net>) |
| Ответы |
Re: schema/db design wrt performance
|
| Список | 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@libertyrms.info> M2P 2A8
+1 416 646 3304 x110
В списке pgsql-performance по дате отправления: