Re: Long running update

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Akash Garg <akash(dot)garg(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Long running update
Date: 2005-08-12 00:10:28
Message-ID: 3167.1123805428@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Akash Garg <akash(dot)garg(at)gmail(dot)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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Peter Fein 2005-08-12 00:11:30 Re: No PUBLIC access by default?
Previous Message Roman Neuhauser 2005-08-11 23:51:42 Re: plphp: PHP Warning: Call-time pass-by-reference has been deprecated