| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Magnus Hagander <magnus(at)hagander(dot)net>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Draft release notes complete |
| Date: | 2012-09-06 01:59:50 |
| Message-ID: | 20120906015950.GL1267@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
* Bruce Momjian (bruce(at)momjian(dot)us) wrote:
> > How often do you want? After all,
> > <http://developer.postgresql.org/docs/postgres/index.html> is
> > presumably going to keep pointing to where it now points.
>
> Well, the old code checked every five minutes, and it rebuilt in 4
> minutes, so there was a max of 10 minutes delay.
I'm a bit mystified why we build them far *more* often than necessary..
Do we really commit documentation updates more than 6 times per day?
Wouldn't it be reasonably straight-forward to set up a commit-hook that
either kicks off a build itself, drops a file marker some place to
signal a cron job to do it, or something similar?
Have to agree with Bruce on this one, for my part. I wonder if the
change to delay the crons was due to lack of proper locking or
tracking, or perhaps a lack of a filter for just changes which would
impact the documentation..
Thanks,
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aidan Van Dyk | 2012-09-06 02:03:55 | Re: Proof of concept: standalone backend with full FE/BE protocol |
| Previous Message | Heikki Linnakangas | 2012-09-06 01:58:50 | Re: Cascading replication on Windows bug |