"Fred Moyer" <fred@redhotpenguin.com> writes:
>> This is just a Seq Scan where a numeric field must be updated to
>> NULL but if I run it you can see that this �simple� query takes
>> forever (7628686.23 ms this is over 2 hours for only updating
>> 747524 records!).
> However updating every row to null with 700k rows is going to take a while
A while, sure, but 2 hours seems excessive to me too. I'm betting that
there are triggers or foreign keys on the table being updated, and that
that's where the time is going. It might be possible to improve that,
but Bobbie hasn't given us enough information.
Another thing that jumps out at me is that this table hasn't been
vacuumed or analyzed recently. The planner thinks there are 3491 rows
when really there are 747524. That's a bit of a big difference. It
won't matter for the UPDATE itself --- a seqscan is a seqscan --- but
it might matter for planning foreign-key queries.
regards, tom lane
