Re: Draft release notes complete - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Draft release notes complete
Date
Msg-id 1336759811.27975.4.camel@vanquo.pezone.net
Whole thread Raw
In response to Re: Draft release notes complete  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
On fre, 2012-05-11 at 11:32 +0200, Magnus Hagander wrote:
> > You are misinterpreting this.  The reason Bruce's link was removed was
> > that the other (official) build was set to run at the same frequency, so
> > Bruce's build was exactly redundant.  The requirement/aspiration to have
> > a few minutes turnaround time continued.
> 
> But the other (official) build was *not* set to run at the same
> frequency. It was set, according to that mail, to run frequently
> enough, but it did not run every 5 minutes. at least not the only
> cronjob I found back then.

I would love to see what cron job job you are referring to.
Unfortunately, I don't have a backup, but I'm pretty sure at one point
it ran every three minutes or so.

> But in the interest of actually being productive - what *is* the
> usecase for needing a 5 minute turnaround time?

I don't exactly know, it was done at the request of users.  A lot of
people wanted to see the documentation of new checkins, just to learn
about how the new features worked.

As a general point, any delay time is going to raise questions, because
it usually won't be easy to find out when things will happen.  So the
"human" maintenance effort will be lower if it runs as soon as possible.




pgsql-hackers by date:

Previous
From: Jeff Janes
Date:
Subject: Re: Draft release notes complete
Next
From: Tom Lane
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Ensure age() returns a stable value rather than the latest value