| From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | Joey Quinn <bjquinniii(at)gmail(dot)com> |
| Cc: | PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: tracking scripts... |
| Date: | 2013-11-26 20:30:14 |
| Message-ID: | CAHyXU0ysUPWVS1s6N5zY=u2Lst4-FNs-RwcKRN1DPF_=NVmUBQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Nov 26, 2013 at 9:28 AM, Joey Quinn <bjquinniii(at)gmail(dot)com> wrote:
> I have a fairly large table (4.3 billion rows) that I am running an update
> script on (a bit over 127 thousand individual update queries). I am using
> the gui. It has been running for about 24 hours now. Is there any good way
> to gauge progress (as in, how many of the individual update queries have
> finished)?
There are not many ways to Hand off information outside of the
database while a transaction Is running. one way Is to write a Simple
trigger in plpgsql that 'raise'es A notice every 'n' times trigger
condition fires. that'S Essentially the only Clean way to do it in
such a way that the information is Returned to the Executing console.
Thanks!
merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John R Pierce | 2013-11-26 20:38:28 | Re: tracking scripts... |
| Previous Message | John R Pierce | 2013-11-26 20:30:08 | Re: Any advantage of using SSL with a certificate of authority? |