Thread: Out-of-date 8.3 beta docs
It looks like http://www.postgresql.org/docs/8.3/static/index.html is still the beta1 documentation. We've done a good bit of docs work since then --- could someone upload beta3 docs there? regards, tom lane
Tom Lane wrote: > It looks like > http://www.postgresql.org/docs/8.3/static/index.html > is still the beta1 documentation. We've done a good bit of docs work > since then --- could someone upload beta3 docs there? Done. Regards, Dave
Dave Page <dpage@postgresql.org> writes: > Tom Lane wrote: >> It looks like >> http://www.postgresql.org/docs/8.3/static/index.html >> is still the beta1 documentation. We've done a good bit of docs work >> since then --- could someone upload beta3 docs there? > Done. How often are the website mirrors supposed to refresh? It's now seven hours since your message and I'm still seeing old docs there... regards, tom lane
Tom Lane wrote: > Dave Page <dpage@postgresql.org> writes: >> Tom Lane wrote: >>> It looks like >>> http://www.postgresql.org/docs/8.3/static/index.html >>> is still the beta1 documentation. We've done a good bit of docs work >>> since then --- could someone upload beta3 docs there? > >> Done. > > How often are the website mirrors supposed to refresh? It's now seven > hours since your message and I'm still seeing old docs there... Ah - it only rebuilds the docs once a day. I thought we'd increased that frequency now wwwmaster is on a much faster box. I'm running the build manually now - the changes should be visible within an hour or so. /D
Dave Page wrote: > Tom Lane wrote: >> Dave Page <dpage@postgresql.org> writes: >>> Tom Lane wrote: >>>> It looks like >>>> http://www.postgresql.org/docs/8.3/static/index.html >>>> is still the beta1 documentation. We've done a good bit of docs work >>>> since then --- could someone upload beta3 docs there? >>> Done. >> How often are the website mirrors supposed to refresh? It's now seven >> hours since your message and I'm still seeing old docs there... > > Ah - it only rebuilds the docs once a day. I thought we'd increased that > frequency now wwwmaster is on a much faster box. I'm running the build > manually now - the changes should be visible within an hour or so. sounds like something we could easily do to reduce the turn-around times for changes like this ... Stefan
Stefan Kaltenbrunner <stefan@kaltenbrunner.cc> writes:
> Dave Page wrote:
>> Ah - it only rebuilds the docs once a day. I thought we'd increased that
>> frequency now wwwmaster is on a much faster box. I'm running the build
>> manually now - the changes should be visible within an hour or so.
> sounds like something we could easily do to reduce the turn-around times
> for changes like this ...
Given that most of the time the docs don't change from day to day,
it seems like timed rebuilds are a waste of cycles. Can't it be
set up with some kind of trigger arrangement? Or at least a quick
check in the script to see if anything's changed?
regards, tom lane
Tom Lane wrote: > Stefan Kaltenbrunner <stefan@kaltenbrunner.cc> writes: >> Dave Page wrote: >>> Ah - it only rebuilds the docs once a day. I thought we'd increased that >>> frequency now wwwmaster is on a much faster box. I'm running the build >>> manually now - the changes should be visible within an hour or so. > >> sounds like something we could easily do to reduce the turn-around times >> for changes like this ... > > Given that most of the time the docs don't change from day to day, > it seems like timed rebuilds are a waste of cycles. Can't it be > set up with some kind of trigger arrangement? Or at least a quick > check in the script to see if anything's changed? yeah I was wondering if we maybe should do something similiar for checkins to the pgweb repository in general (ie have a commit trigger a rebuild) I'm not so sure how the doc building process works in detail to see if that would be feasible. Stefan
Stefan Kaltenbrunner wrote: > Tom Lane wrote: > > Stefan Kaltenbrunner <stefan@kaltenbrunner.cc> writes: > >> Dave Page wrote: > >>> Ah - it only rebuilds the docs once a day. I thought we'd increased that > >>> frequency now wwwmaster is on a much faster box. I'm running the build > >>> manually now - the changes should be visible within an hour or so. > > > >> sounds like something we could easily do to reduce the turn-around times > >> for changes like this ... > > > > Given that most of the time the docs don't change from day to day, > > it seems like timed rebuilds are a waste of cycles. Can't it be > > set up with some kind of trigger arrangement? Or at least a quick > > check in the script to see if anything's changed? > > yeah I was wondering if we maybe should do something similiar for > checkins to the pgweb repository in general (ie have a commit trigger a > rebuild) I'm not so sure how the doc building process works in detail to > see if that would be feasible. Uh, why not just point them to the developer docs? http://developer.postgresql.org/pgdocs/postgres/index.html -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://postgres.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +
On Wed, 2007-11-21 at 20:51 +0100, Stefan Kaltenbrunner wrote: > Tom Lane wrote: > > Stefan Kaltenbrunner <stefan@kaltenbrunner.cc> writes: > >> Dave Page wrote: > >>> Ah - it only rebuilds the docs once a day. I thought we'd increased that > >>> frequency now wwwmaster is on a much faster box. I'm running the build > >>> manually now - the changes should be visible within an hour or so. > > > >> sounds like something we could easily do to reduce the turn-around times > >> for changes like this ... > > > > Given that most of the time the docs don't change from day to day, > > it seems like timed rebuilds are a waste of cycles. Can't it be > > set up with some kind of trigger arrangement? Or at least a quick > > check in the script to see if anything's changed? > > yeah I was wondering if we maybe should do something similiar for > checkins to the pgweb repository in general (ie have a commit trigger a > rebuild) I'm not so sure how the doc building process works in detail to > see if that would be feasible. The simplest thing is probably to have the docs load script output a line that says "hey, don't forget to run <command x> now"... It's not like we update the docs often, and the loader step has to be manual anyway, so I think that's good enough. //Magnus
On Wed, 2007-11-21 at 17:39 -0500, Bruce Momjian wrote: > Stefan Kaltenbrunner wrote: > > Tom Lane wrote: > > > Stefan Kaltenbrunner <stefan@kaltenbrunner.cc> writes: > > >> Dave Page wrote: > > >>> Ah - it only rebuilds the docs once a day. I thought we'd increased that > > >>> frequency now wwwmaster is on a much faster box. I'm running the build > > >>> manually now - the changes should be visible within an hour or so. > > > > > >> sounds like something we could easily do to reduce the turn-around times > > >> for changes like this ... > > > > > > Given that most of the time the docs don't change from day to day, > > > it seems like timed rebuilds are a waste of cycles. Can't it be > > > set up with some kind of trigger arrangement? Or at least a quick > > > check in the script to see if anything's changed? > > > > yeah I was wondering if we maybe should do something similiar for > > checkins to the pgweb repository in general (ie have a commit trigger a > > rebuild) I'm not so sure how the doc building process works in detail to > > see if that would be feasible. > > Uh, why not just point them to the developer docs? > > http://developer.postgresql.org/pgdocs/postgres/index.html > developer.postgresql.org is frequently overloaded or just not accessible. www.postgresql.org is distributed for performance and redundancy. It also formats the docs "nicer" in the archives. And it has docs searchable. The list goes on.. :-P //Magnus