Re: performance problems on updates on large tables with indexes - Mailing list pgsql-bugs

From Tom Lane
Subject Re: performance problems on updates on large tables with indexes
Date
Msg-id 8483.1014846115@sss.pgh.pa.us
Whole thread Raw
In response to performance problems on updates on large tables with indexes  (Reinhard Max <max@suse.de>)
List pgsql-bugs
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

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: function tree_level(varchar) (from OpenACS) no longer work under 7.2
Next
From: Tom Lane
Date:
Subject: Re: missing foreign key fails silently using COPY