Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id 72FA42E002F for ; Wed, 11 Jun 2008 11:13:51 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 25852-05 for ; Wed, 11 Jun 2008 11:13:41 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.177]) by developer.postgresql.org (Postfix) with ESMTP id F15042E002E for ; Wed, 11 Jun 2008 11:13:46 -0300 (ADT) Received: by py-out-1112.google.com with SMTP id d37so1322198pye.29 for ; Wed, 11 Jun 2008 07:13:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=i2+Y+cGuIw9SWX7d81txzwn2M8OEr2zPYqmAgFd/4aY=; b=WZKLfsSjeZ5l6ATJJRIC+AULLXFMLPPOrEw8og2p8X4KlE6oUSJsUGlTZqAgSDKu/y jHDP/CtonZt22g7khFlbqw2r9eOUZsRfvHyB7OG4l5mVvHiftFWoilOjZA0+d6tsOkkO LElbGiD0tMwD6oEvx2F2y5PKDh03QJMBWzMfM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=fWRESbfRMutDWClv01yneAy7ajfItVYygS3zH/5gYa5pi0NIfrZr26f2C3HqjsxOxl KfAX8xU++9d7nO/dCCYvPw1KeYqW7Ilqqxy7XQIfvEbpboZYUQGjjNX+YTK8VYMl9r+y TeD0olLDDoYlZAm1OSarCevwR/JZNhKEDA2I8= Received: by 10.114.235.8 with SMTP id i8mr6565840wah.194.1213193624928; Wed, 11 Jun 2008 07:13:44 -0700 (PDT) Received: by 10.114.130.17 with HTTP; Wed, 11 Jun 2008 07:13:44 -0700 (PDT) Message-ID: Date: Wed, 11 Jun 2008 08:13:44 -0600 From: "Scott Marlowe" To: "Zoltan Boszormenyi" Subject: Re: Scalability question Cc: "PostgreSQL Performance" , "Hans-Juergen Schoenig" In-Reply-To: <484FA134.7030807@cybertec.at> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <484FA134.7030807@cybertec.at> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200806/48 X-Sequence-Number: 30398 On Wed, Jun 11, 2008 at 3:56 AM, 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. 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.