From: Marc G. Fournier <scrappy@hub.org>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: John Summerfield <pgtest@os2.ami.com.au>
Cc: Peter Eisentraut <peter_e@gmx.net>
Cc: PostgreSQL Development <pgsql-hackers@postgresql.org>
Subject: Re: CVS changes
Date: Tue, 2 Oct 2001 12:55:26 -0400 (EDT)
Message-ID: <20011002125455.R77860-100000@mail1.hub.org> (raw)
In-Reply-To: <200110021614.f92GEA511627@candle.pha.pa.us>
Ummmm ... I thought we weren't going to do this, but were going to fix the
proper build process?
On Tue, 2 Oct 2001, Bruce Momjian wrote:
> > On Sun, 30 Sep 2001, Bruce Momjian wrote:
> >
> >
> > > > On Sun, 30 Sep 2001, Bruce Momjian wrote:
> > > >
> > > >
> > > > > >
> > > > > >
> > > > > > just about to be moved to the new server, now that the new 18gi drive has
> > > > > > been installed ... plan on getting that done this afternoon ...
> > > > >
> > > > > Don't rush. I am setting up my system to check the SGML docs every 15
> > > > > minutes and rebuild if necessary. Overnight builds are not frequent
> > > > >
> > > > Would it not be better to provide a means for developers to cause the rebuild on demand? A 15-minute wait doesn't seem convenient to me.
> > >
> > > Yep, but it takes 15 minutes to build anyway, so I figured I would check
> > > very 15 minutes and adding another 15, that makes 1/2 hour. We don't
> > > have a mechanism to build only a few html files. You have to do the
> > > whole thing.
> > >
> > > Suggestions?
> >
> > I don't know enough about how it works (or doesn't), but the
> > delay looks worse.
> >
> > Add the delay for "missing the bus" and you're out to a 45-minute
> > delay.
>
> True.
>
> > The need for on-demand is even greater, even something done
> > crudely:
> >
> > If a build's in process, flag the need.
>
> Added. I realized that I could have two running at the same time, which
> would be a disaster.
>
> > When the build completes, check if it has to be done again.
>
> Great idea! Added.
>
> > I assume that updates aren't so frequent that you'd be constantly
> > rebuilding, or so infrequently a missed rebuild would cause
> > serious problems.
>
> Yep.
>
> > Perhaps a way to check if a rebuild's in process so that if it's
> > slower than usual a developer can see it's not forgotten (or
> > who else is doing one).
>
> Script attached. I could poll cvs more frequently but it seems rude to
> hit the cvs server more frequently than every 15 minutes. If people
> want it polled more frequently, and Marc doesn't mind, I can change the
> polling interval here.
>
> Also, I added something that will show the files modified in the current
> build.
>
> --
> Bruce Momjian | http://candle.pha.pa.us
> pgman@candle.pha.pa.us | (610) 853-3000
> + If your life is a hard drive, | 830 Blythe Avenue
> + Christ can be your backup. | Drexel Hill, Pennsylvania 19026
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: scrappy@hub.org, pgman@candle.pha.pa.us, pgtest@os2.ami.com.au, peter_e@gmx.net, pgsql-hackers@postgresql.org
Subject: Re: CVS changes
In-Reply-To: <20011002125455.R77860-100000@mail1.hub.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox