| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Greg Stark <gsstark(at)mit(dot)edu> |
| Cc: | Hannu Krosing <hannu(at)skype(dot)net>, Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Online index builds |
| Date: | 2006-07-16 01:37:58 |
| Message-ID: | 44B99876.3060604@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> That said I'm not sure how much I can do here. For a substantial index we
> should expect most of the time will be spent in the tuplesort. It's hard to
> see how to get any sort of progress indicator out of there and as long as we
> can't it's hard to see the point of getting one during the heap scan or any of
> the other i/o operations.
Well from a DBA perspective, just knowing that "something" productive is
happening is useful.
When using vacuum I almost always use vacuum verbose, just so I have an
idea of what is going on.
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-07-16 01:57:06 | pgwin32_backend_usleep seems overly cute/confusing |
| Previous Message | Hiroshi Saito | 2006-07-16 01:33:37 | Re: PostmasterHandl_patch of win32 |