Re: Updates on large tables are extremely slow

Ok, if all 21 are affected, I can understand the problem.
But allow me to say that this is a "functional error"

On 13 Jun 2005, at 18:02, Richard Huxton wrote:

> Yves Vindevogel wrote:
>> I forgot cc
>> Begin forwarded message:
>>> From: Yves Vindevogel <yves(dot)vindevogel(at)implements(dot)be>
>>> Date: Mon 13 Jun 2005 17:45:19 CEST
>>> To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
>>> Subject: Re: [PERFORM] Updates on large tables are extremely slow
>>>
>>> Yes, but if I update one column, why should PG update 21 indexes ?
>>> There's only one index affected !
>
> No - all 21 are affected. MVCC creates a new row on disk.
>
> --
> Richard Huxton
> Archonet Ltd
>
>
Met vriendelijke groeten,
Bien à vous,
Kind regards,

Yves Vindevogel
Implements