Re: Locking
| От | Peter Eisentraut |
|---|---|
| Тема | Re: Locking |
| Дата | |
| Msg-id | Pine.LNX.4.30.0102191821060.977-100000@peter.localdomain обсуждение исходный текст |
| Ответ на | Locking (Simon Attwell <attwell@binc.net>) |
| Список | pgsql-general |
Simon Attwell writes: > How does postgresql deal with locking when one has a large select query running > on a > 700,000 row table, when there are inserts pending for that table. The insert and select can happen in parallel. See http://www.postgresql.org/users-lounge/docs/7.0/postgres/mvcc.htm for the gory details. > I have an application that does a _lot_ of inserts, and a frontend that > makes large long laborious select queries on the same tables. > > MySQL has the INSERT DELAYED which allows batch processing of inserts and > allows clients to receive and instant "OK" when doing inserts. No, PostgreSQL doesn't cheat. -- Peter Eisentraut peter_e@gmx.net http://yi.org/peter-e/
В списке pgsql-general по дате отправления: