In response to Bill Thoen <bthoen@gisnet.com>:
> Doesn't look like that's the problem. I moved my table over to another
> Linux box running PG 8.3 and update performance was pretty bad there as
> well. In the time that PG 8.3 was struggling with update there I created
> a copy of my table on my PG 8.1 machine and inserted all columns with
> one containing the altered values I wanted and that took less than two
> minutes. Meanwhile, a half-hour later, my PG 8.3 machine was still
> thrashing away trying to update that one column that's not even part of
> any index..
>
> Something is really wrong with UPDATE in PostgreSQL I think.
That's an interesting theory, although it's completely wrong and founded
in ridiculosity. If something were "really wrong with UPDATE" in every
version of PostgreSQL, you'd be reading about it on the mailing lists,
and you won't.
What I suspect is that the typical tuning advice applies here. I don't
see any information about your configuration or your hardware setup.
* What are shared_buffers set at?
* What do the checkpoint configs look like?
* In general, what does your postgresql.conf look like, how much tuning
have you done?
* What is your hardware setup? You're not running RAID 5 are you?
--
Bill Moran
Collaborative Fusion Inc.
http://people.collaborativefusion.com/~wmoran/
wmoran@collaborativefusion.com
Phone: 412-422-3463x4023
