Re: update query taking 24+ hours

Ken <postgres(at)kwasnicki(dot)com> writes:
> I have postgres 8.1 on a linux box: 2.6Ghz P4, 1.5GB ram, 320GB hard
> drive. I'm performing an update between two large tables and so far
> it's been running for 24+ hours.
> UPDATE Master SET val2=Import.val WHERE Master.x=Import.x AND
> Master.y=Import.y;

What does EXPLAIN say about that? (Don't try EXPLAIN ANALYZE,
but a plain EXPLAIN should be quick enough.)

> Both tables have indexes on the x and y columns. Will that help?

A two-column index would have helped a lot more, probably, although
with so many rows to process I'm not sure that indexes are useful
anyway. For really bulk updates a hashjoin or sort-and-mergejoin
plan is probably the best bet.

BTW, both of those would require plenty of work_mem to run fast
... what have you got work_mem set to?

And possibly even more to the point, do you have any foreign key
constraints leading into or out of the Master table?

regards, tom lane