Akash Garg <akash.garg@gmail.com> writes:
> I currently running an update statement that updates every row in a
> very large table. This query will obviously take a long time to run.
> My question -- is there any way to know how much time it will take
> once it starts? Even something that could help me approximate the
> speed at which it's doing the update would be helpful.
If it's doing a seqscan then strace'ing the backend and noting which
blocks it's reading would give you a good hint. If it's an indexscan
there's probably no very easy way to tell ...
regards, tom lane
