| From: | Harry Mantheakis <harry(dot)mantheakis(at)riskcontrollimited(dot)com> |
|---|---|
| To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | Claudio Freire <klaussfreire(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Long Running Update |
| Date: | 2011-06-24 16:29:41 |
| Message-ID: | 4E04BB75.4070403@riskcontrollimited.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Thank you so much for all the feedback, Kevin - much appreciated.
I have stopped the all-in-one-go update from executing, and now I am
executing a series of statements, each constrained to update no more
than 100,000 records at a time.
Interesting fact: updating 100,000 rows takes 5 seconds. Quick.
I tried updating 1 million rows in one go, and the statement was still
running after 25 minutes, before I killed it!
So I am now executing an SQL script with almost 800 separate
update-statements, each set to update 100K records, and the thing is
trundling along nicely. (I am fortunate enough to be surrounded by
MatLab users, one of whom generated the 800-statement file in one minute
flat!)
Many thanks again for all the info.
Kind regards
Harry Mantheakis
London, UK
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Harry Mantheakis | 2011-06-24 16:31:38 | Re: Long Running Update |
| Previous Message | Greg Smith | 2011-06-24 16:18:49 | Re: Cost of creating an emply WAL segment |