Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Bad performance in bulky updates
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: carlos(dot)reimer(at)opendb(dot)com(dot)br
- Cc: "Pgsql-General(at)Postgresql(dot)Org" <pgsql-general(at)postgresql(dot)org>
- Subject: Re: Bad performance in bulky updates
- Date: Mon, 30 Oct 2006 21:02:31 -0500
"Carlos H. Reimer" <carlos(dot)reimer(at)opendb(dot)com(dot)br> writes: > When one of the biggest tables has all lines updated for example, it takes > at about 30 minutes for processing. If we drop all indexes (21) and let only > the primary index the same update takes 2 minutes. 21 indexes?? If update performance is important then you should try to economize on indexes. Do you have evidence that each of those indexes is worth its update costs? regards, tom lane
- References:
- Bad performance in bulky updates
- From: Carlos H. Reimer
- Bad performance in bulky updates
- Prev by Date: Bad performance in bulky updates
- Next by Date: Re: postgresql books and convertion utilities
- Previous by thread: Bad performance in bulky updates
- Next by thread: Re: Bad performance in bulky updates
- Indexes: