Jessica Richard wrote: > 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)? All PostgreSQL indexes are like the non-clustered ones in Sybase or SQL Server. > 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? Create the indexes you actually need to make the selects and updates fast, just make sure you don't create any unnecessary ones. Usually, your UPDATEs will also require indexes - only the INSERTs actually are losing. //Magnus
