| From: | Roman Neuhauser <neuhauser(at)sigpipe(dot)cz> |
|---|---|
| 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-11 23:32:07 |
| Message-ID: | 20050811233206.GA24601@isis.sigpipe.cz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
# akash(dot)garg(at)gmail(dot)com / 2005-08-11 16:17:09 -0700:
> Hello,
> 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.
Yeah, it would be nice if select, insert, update, delete could
be set to log their progress at configured intervals.
--
How many Vietnam vets does it take to screw in a light bulb?
You don't know, man. You don't KNOW.
Cause you weren't THERE. http://bash.org/?255991
| From | Date | Subject | |
|---|---|---|---|
| Next Message | CSN | 2005-08-11 23:49:25 | Re: plphp: PHP Warning: Call-time pass-by-reference has been deprecated |
| Previous Message | Akash Garg | 2005-08-11 23:17:09 | Long running update |