Date: Wed, 11 Jun 2008 09:34:38 -0400
From: Alvaro Herrera <alvherre@commandprompt.com>
To: Zoltan Boszormenyi <zb@cybertec.at>
Cc: PostgreSQL Performance <pgsql-performance@postgresql.org>,
	Hans-Juergen Schoenig <hs@cybertec.at>
Subject: Re: Scalability question
Message-ID: <20080611133438.GD5352@alvh.no-ip.org>
References: <484FA134.7030807@cybertec.at>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <484FA134.7030807@cybertec.at>
User-Agent: Mutt/1.5.18 (2008-05-17)

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.