| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Why does analyze_new_cluster.sh use sleep? |
| Date: | 2012-08-23 21:05:45 |
| Message-ID: | 20120823210545.GB10337@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Aug 23, 2012 at 02:17:44AM -0400, Peter Eisentraut wrote:
> The script analyze_new_cluster.sh output by pg_upgrade contains several
> "sleep" calls (see contrib/pg_upgrade/check.c). What is the point of
> this? If the purpose of this script is to get the database operational
> again as soon as possible, waiting a few seconds doing nothing surely
> isn't helping.
>
> I could maybe see the point of waiting a bit between the different
> vacuumdb calls, to catch some breath, but the one before the first call
> to vacuumdb is highly dubious to me.
The sleep is there so the user can read the status message, in case it
scrolls off the screen once the next stage starts.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2012-08-23 23:06:18 | Re: 9.2RC1 wraps this Thursday ... |
| Previous Message | Bruce Momjian | 2012-08-23 21:03:36 | Re: Is this an appropriate item? |