From: Harry Mantheakis <harry.mantheakis@riskcontrollimited.com>
To: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: Claudio Freire <klaussfreire@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Long Running Update
Date: Fri, 24 Jun 2011 17:29:41 +0100
Message-ID: <4E04BB75.4070403@riskcontrollimited.com> (raw)
In-Reply-To: <4E0462FA020000250003EBB8@gw.wicourts.gov>
References: <4E035649.20007@riskcontrollimited.com>
<BANLkTi=gt+LpTijBxtDp+k49fLFOFFZWQw@mail.gmail.com>
<4E0472AB.9090507@riskcontrollimited.com>
<4E0462FA020000250003EBB8@gw.wicourts.gov>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: harry.mantheakis@riskcontrollimited.com, Kevin.Grittner@wicourts.gov, klaussfreire@gmail.com
Subject: Re: Long Running Update
In-Reply-To: <4E04BB75.4070403@riskcontrollimited.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox