| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Simon Attwell <attwell(at)binc(dot)net> |
| Cc: | <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Locking |
| Date: | 2001-02-19 17:24:45 |
| Message-ID: | Pine.LNX.4.30.0102191821060.977-100000@peter.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)gmx(dot)net http://yi.org/peter-e/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2001-02-19 17:54:15 | Re: Re: Postgres slowdown on large table joins |
| Previous Message | Tom Lane | 2001-02-19 17:12:02 | Re: Locking |