Re: performance problems on updates on large tables with indexes

Reinhard Max <max@suse.de> writes:
> It has a unique index on id, non-unique indexes on all othe columns,
> and contains approx. 350000 rows.

Do you actually *need* an index on every single column?  How many of
those columns are you actually going to use for searches on a frequent
basis?

Creating an index is a straightforward tradeoff of more time spent for
updates to save on searches.  I suspect you have made a bad tradeoff.

            regards, tom lane