Skip site navigation (1) Skip section navigation (2)

Re: index performance

From: Chander Ganesan <chander(at)otg-nc(dot)com>
To: Jessica Richard <rjessil(at)yahoo(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: index performance
Date: 2008-05-23 16:18:23
Message-ID: 4836EE4F.5060304@otg-nc.com (view raw or flat)
Thread:
Lists: pgsql-admin
> I have a large table with about 2 million rows and it will keep growing...
>
> I need to do update/inserts, and select as well.
>
> An index will speed up the select, but it will slow down the updates.
>
> Are all Postgres indexes ordered? i.e., with every update, the index 
> pages will have to be physically reordered?
>
> Does Postgres have any kind of non-ordered indexes (like Syabse's 
> non-clustered index)?
>
> What is the common way to take care of the performance issue when you 
> have to do both update and select on the same large table?
You might consider table partitioning and enabling constraint exclusion. 

-- 
Chander Ganesan
Open Technology Group, Inc.
One Copley Parkway, Suite 210
Morrisville, NC  27560
919-463-0999/877-258-8987
http://www.otg-nc.com
Ask me about OTG's Expert On-Site & Public enrollment PostgreSQL, PostGIS, and other Open Source courses.

In response to

pgsql-admin by date

Next:From: Blakely, Jerel (Mission Systems)Date: 2008-05-23 16:23:23
Subject: How do I force users to change their password?
Previous:From: Guy DeleeuwDate: 2008-05-23 15:41:05
Subject: error on my apache log

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group