> 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.
Open Technology Group, Inc.
One Copley Parkway, Suite 210
Morrisville, NC 27560
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 Deleeuw||Date: 2008-05-23 15:41:05|
|Subject: error on my apache log|