From: Alvaro Herrera <alvherre@commandprompt.com>
To: Zoltan Boszormenyi <zb@cybertec.at>
Cc: PostgreSQL Performance <pgsql-performance@postgresql.org>
Cc: Hans-Juergen Schoenig <hs@cybertec.at>
Subject: Re: Scalability question
Date: Wed, 11 Jun 2008 09:34:38 -0400
Message-ID: <20080611133438.GD5352@alvh.no-ip.org> (raw)
In-Reply-To: <484FA134.7030807@cybertec.at>
References: <484FA134.7030807@cybertec.at>
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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: alvherre@commandprompt.com, zb@cybertec.at, hs@cybertec.at
Subject: Re: Scalability question
In-Reply-To: <20080611133438.GD5352@alvh.no-ip.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox