From: Scott Marlowe <scott.marlowe@gmail.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 08:13:44 -0600
Message-ID: <dcc563d10806110713n7e1cff25ua527c68f09d8000c@mail.gmail.com> (raw)
In-Reply-To: <484FA134.7030807@cybertec.at>
References: <484FA134.7030807@cybertec.at>
On Wed, Jun 11, 2008 at 3:56 AM, Zoltan Boszormenyi <zb@cybertec.at> 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.
PostgreSQL supports initial fill rates of < 100% for indexes, so set
it to 50% filled and new entries that live near current entries will
have room to be added without having the split the btree.
PostgreSQL also allows you to easily put your indexes on other
paritions / drive arrays etc...
PostgreSQL does NOT store visibility info in the indexes, so they stay
small and updates to them are pretty fast.
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: scott.marlowe@gmail.com, zb@cybertec.at, hs@cybertec.at
Subject: Re: Scalability question
In-Reply-To: <dcc563d10806110713n7e1cff25ua527c68f09d8000c@mail.gmail.com>
* 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