Skip site navigation (1) Skip section navigation (2)

Re: Long update progress

From: <mallah(at)trade-india(dot)com>
To: <amarden(at)usa(dot)net>
Cc: <pgsql-admin(at)postgresql(dot)org>, <pgsql-general(at)postgresql(dot)org>
Subject: Re: Long update progress
Date: 2002-07-19 12:46:38
Message-ID: 62064.203.196.129.235.1027082798.squirrel@mail.trade-india.com (view raw or flat)
Thread:
Lists: pgsql-adminpgsql-general
create a sequence and somehow involve it in a dummy manner in the update...

do a select  current_val('sequence') to see how far updates have gone...

can we see the update stmt?

regds
mallah.


> 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?
>
> Cheers
>
> Andy
>
>
>
> ---------------------------(end of
> broadcast)--------------------------- TIP 5: Have you checked our
> extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html



-----------------------------------------
Get your free web based email at trade-india.com.
   "India's Leading B2B eMarketplace.!"
http://www.trade-india.com/



In response to

Responses

pgsql-admin by date

Next:From: Andy MardenDate: 2002-07-19 12:52:27
Subject: Re: Long update progress
Previous:From: Jan D'HondtDate: 2002-07-19 12:43:23
Subject: Re: Disabling case sensitivity

pgsql-general by date

Next:From: Andy MardenDate: 2002-07-19 12:52:27
Subject: Re: Long update progress
Previous:From: Steve BrettDate: 2002-07-19 12:46:36
Subject: Re: References for PostgreSQL

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group