Long update progress

From: "Andy Marden" <amarden(at)usa(dot)net>
To: pgsql-admin(at)postgresql(dot)org, pgsql-general(at)postgresql(dot)org
Subject: Long update progress
Date: 2002-07-19 12:31:52
Message-ID: ah90s2$1k2f$1@news.hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-admin pgsql-general

We have an database batch update process running. It runs normally and takes
around 6 hours. This is dealing with a much larger data set after an error
correction. It's been running for 6 days now and people are getting twitchy
that it might not finish. Is there any way (accepting that more preparation
would, in retrospect, have been better) to tell how far we're got. This
iterates round a cursor and updates individual rows. The trouble is it
commits once at the end.

The ideal would be to find a way of doing a dirty read against the table
that is bing updated. Then we'd know how many rows had been processed.

Any ideas?




Browse pgsql-admin by date

  From Date Subject
Next Message Jan D'Hondt 2002-07-19 12:43:23 Re: Disabling case sensitivity
Previous Message l.malaspina 2002-07-19 10:45:47 REINDEX problem : ERROR: MemoryContextAlloc: invalid request size 2973040639

Browse pgsql-general by date

  From Date Subject
Next Message Tom Jenkins 2002-07-19 12:33:23 Re: References for PostgreSQL
Previous Message Steve Brett 2002-07-19 12:30:41 Re: References for PostgreSQL