On Sun, Aug 26, 2012 at 11:12:15PM -0400, Peter Eisentraut wrote:
> On Fri, 2012-08-24 at 08:19 -0400, Bruce Momjian wrote:
> > Well, the idea is that the script is running stages, and your system is
> > mostly useful after the first stage is done. I don't see a keypress as
> > helping there. I t
On Fri, 2012-08-24 at 08:19 -0400, Bruce Momjian wrote:
> Well, the idea is that the script is running stages, and your system is
> mostly useful after the first stage is done. I don't see a keypress as
> helping there. I think this is different from the vacuumdb case.
Well, this is all debatabl
On Thu, Aug 23, 2012 at 11:15:06PM -0400, Peter Eisentraut wrote:
> On Thu, 2012-08-23 at 17:05 -0400, Bruce Momjian wrote:
> > 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 co
On Thu, 2012-08-23 at 17:05 -0400, Bruce Momjian wrote:
> 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
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 so
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.
