| From: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Postgresql General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: progress of long running operation |
| Date: | 2012-12-27 20:10:19 |
| Message-ID: | CF12D331-2BD6-4495-AF9C-76FF53400BAB@elevated-dev.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Dec 27, 2012, at 12:46 PM, Tom Lane wrote:
> Or you could run contrib/pgstattuple's pgstattuple() function every so
> often --- it will report the uncommitted tuples as "dead", which is
> inaccurate, but you'd be able to see how fast the number is increasing.
That's exactly the kind of thing I was hoping for. I'm actually inserting into an empty table, so "dead" tuples would be dead accurate in my case ;-)
Or I could suck it up and do them in batches instead of one giant pass...
--
Scott Ribe
scott_ribe(at)elevated-dev(dot)com
http://www.elevated-dev.com/
(303) 722-0567 voice
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Morgan Lloyd | 2012-12-27 20:19:46 | Re: libpq thread safety |
| Previous Message | Tom Lane | 2012-12-27 19:46:48 | Re: progress of long running operation |