| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Zoltan Boszormenyi <zb(at)cybertec(dot)at> |
| Cc: | PostgreSQL Performance <pgsql-performance(at)postgresql(dot)org>, Hans-Juergen Schoenig <hs(at)cybertec(dot)at> |
| Subject: | Re: Scalability question |
| Date: | 2008-06-11 13:34:38 |
| Message-ID: | 20080611133438.GD5352@alvh.no-ip.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Zoltan Boszormenyi wrote:
> Hi,
>
> I got a question about scalability in high volume insert situation
> where the table has a primary key and several non-unique indexes
> on other columns of the table. How does PostgreSQL behave
> in terms of scalability? The high volume of inserts comes from
> multiple transactions.
btree and gist indexes can have multiple concurrent insertions in
flight. A potential for blocking is in UNIQUE indexes: if two
transactions try to insert the same value in the unique index, the
second one will block until the first transaction finishes.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2008-06-11 14:13:44 | Re: Scalability question |
| Previous Message | Zoltan Boszormenyi | 2008-06-11 10:35:54 | Re: Scalability question |