Received: from localhost (unknown [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 2F7BF2E01BF for ; Wed, 9 Jan 2008 01:56:41 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 01013-08 for ; Wed, 9 Jan 2008 01:56:32 -0400 (AST) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id B94152E0282 for ; Wed, 9 Jan 2008 01:55:25 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id m095tNJa028137; Wed, 9 Jan 2008 00:55:23 -0500 (EST) To: Alvaro Herrera cc: pgsql-docs@postgresql.org Subject: Re: 'make draft' and HTML.index In-reply-to: <20080109054155.GG20913@alvh.no-ip.org> References: <20080109054155.GG20913@alvh.no-ip.org> Comments: In-reply-to Alvaro Herrera message dated "Wed, 09 Jan 2008 02:41:55 -0300" Date: Wed, 09 Jan 2008 00:55:23 -0500 Message-ID: <28136.1199858123@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200801/10 X-Sequence-Number: 4739 Alvaro Herrera writes: > Currently, we generate HTML.index by running openjade in normal mode, > and then rerunning if we detect that the HTML.index file changed. This > is a waste -- with patched docbook.dsl, it takes 8 seconds to generate > the index file on my system, whereas the regular openjade run takes > 1:30. So on a clean start it takes 3 minutes to generate the docs. There's another problem with the current technology for that, which is that it not infrequently takes *three* iterations to converge, meaning it's faster to "make clean all" than to try to use the existing state. I have not looked into why, but certainly this isn't very satisfactory. regards, tom lane