| From: | Rémi Cura <remi(dot)cura(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 16:16:08 |
| Message-ID: | CAJvUf_uRct3-4UpZid4WDkU5kFq-oGBDqrK_cm+ueszQY6wMog@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Now it's too late,
but maybe you could allow to not use a single transaction ( but instead
127k transactions).4
Then at the end of every transaction you could print something in gui
(print for pgscript, raise for plpgsql) or execute a command to write in a
file (copy for instance).
It would also be in the log, but not so clear.
Cheers,
Rémi-C
2013/11/26 Joey Quinn <bjquinniii(at)gmail(dot)com>
> 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)?
>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vick Khera | 2013-11-26 16:20:11 | Re: tracking scripts... |
| Previous Message | Joey Quinn | 2013-11-26 15:28:31 | tracking scripts... |