index performance on large tables with update and insert

From: Jessica Richard <rjessil(at)yahoo(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Subject: index performance on large tables with update and insert
Date: 2008-05-23 13:21:17
Message-ID: 334290.54805.qm@web56401.mail.re3.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

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?

Thanks,
Jessica

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Kevin Grittner 2008-05-23 15:15:29 IBM ServRAID-MR10M / LSI1078ROC advice
Previous Message Reid Thompson 2008-05-23 12:50:23 Re: Quad Xeon or Quad Opteron?