Received: from maia.hub.org (maia-3.hub.org [200.46.204.243])
	by mail.postgresql.org (Postfix) with ESMTP id 458FF1337B93
	for <pgsql-docs-postgresql.org@mail.postgresql.org>;
	Fri,  8 Apr 2011 12:07:37 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia,
	port 10024) with ESMTP id 29983-01-10
	for <pgsql-docs-postgresql.org@mail.postgresql.org>;
	Fri,  8 Apr 2011 15:07:26 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130])
	by mail.postgresql.org (Postfix) with ESMTP id D80CE1337BBA
	for <pgsql-docs@postgresql.org>; Fri,  8 Apr 2011 12:07:22 -0300 (ADT)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id p38F7KIN011934;
	Fri, 8 Apr 2011 11:07:20 -0400 (EDT)
To: Thom Brown <thom@linux.com>
cc: pgsql-docs <pgsql-docs@postgresql.org>
Subject: Re: CREATE DATABASE appears twice 
In-reply-to: <BANLkTimd5XGZMbaepWrYPGtzQSTQ9wpbQA@mail.gmail.com> 
References: <BANLkTimd5XGZMbaepWrYPGtzQSTQ9wpbQA@mail.gmail.com>
Comments: In-reply-to Thom Brown <thom@linux.com>
	message dated "Fri, 08 Apr 2011 15:29:00 +0100"
Date: Fri, 08 Apr 2011 11:07:20 -0400
Message-ID: <11933.1302275240@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-1.91 tagged_above=-5 required=5 tests=BAYES_00=-1.9,
	T_RP_MATCHES_RCVD=-0.01
X-Spam-Level: 
X-Archive-Number: 201104/62
X-Sequence-Number: 6633

Thom Brown <thom@linux.com> writes:
> In the index of the documentation, CREATE DATABASE appears above
> CREATE AGGREGATE, and also in the correct place further down the
> index.  This is because it actually contains a newline and/or
> additional spaces in the indexterm definition.  Could someone please
> fix this?  I'd submit a patch, but then I can't test it on the only
> system I have available at the moment.

[ experiments ... ]  Apparently, any extra whitespace in the argument of
<indexterm> causes the indexer to think it's not the identical index
term.  Ugh.  This seems like a toolchain bug, but I confirm the same
behavior.  There appear to be a few other cases, though the other ones
may not be causing any visible misbehavior at the moment.

			regards, tom lane