Ben Campbell wrote:
> I _think_ the reason it takes so long is that postgresql doesn't
> modify rows in place - it creates an entry for the modified row and
> zaps the old one. So by touching _every_ row I'm basically forcing it
> to rebuild my whole database... I've got about 2 million rows in
> 'articles'.
> There are a few indexes on columns in 'articles' which obviously will
> slow things down too.
at the expense of disk space, try setting fill_factor for that table to
something like 70 instead of the default 100.
