Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id F24C563265B for ; Wed, 1 Sep 2010 15:57:46 -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 55996-06 for ; Wed, 1 Sep 2010 18:57:39 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from spinlock.commandprompt.com (host-215.commandprompt.net [207.173.203.215]) by mail.postgresql.org (Postfix) with ESMTP id 8B541632369 for ; Wed, 1 Sep 2010 15:57:39 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by spinlock.commandprompt.com (Postfix) with ESMTP id DB54A348012; Wed, 1 Sep 2010 11:57:37 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at commandprompt.com Received: from spinlock.commandprompt.com ([127.0.0.1]) by localhost (spinlock.commandprompt.com.commandprompt.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v7cTudYu2Iy2; Wed, 1 Sep 2010 11:57:31 -0700 (PDT) Received: from perhan.alvh.no-ip.org (200-126-90-175.bk6-dsl.surnet.cl [200.126.90.175]) by spinlock.commandprompt.com (Postfix) with ESMTPSA id 9F9D6348011; Wed, 1 Sep 2010 11:57:31 -0700 (PDT) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 408A26E4F3; Wed, 1 Sep 2010 14:57:28 -0400 (CLT) Content-Type: text/plain; charset=UTF-8 Cc: pgsql-docs Subject: Re: Inconsistent index links From: Alvaro Herrera To: Thom Brown In-reply-to: References: Date: Wed, 01 Sep 2010 14:57:28 -0400 Message-Id: <1283366481-sup-7789@alvh.no-ip.org> User-Agent: Sup/git Content-Transfer-Encoding: 8bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-5 required=5 tests=BAYES_00=-1.9 X-Spam-Level: X-Archive-Number: 201009/21 X-Sequence-Number: 6011 Excerpts from Thom Brown's message of mié sep 01 14:21:59 -0400 2010: > Hi all, > > I noticed that all aggregate functions listed in the documentation > index direct to a page listing all the aggregate functions and their > usage, with the exception of count, max, min and sum, which direct to > the aggregate function tutorial page. From the index, these sections > are indistinguishable from one another since they share the same page > name. I'm wondering if one should be named differently, like > Aggregate Functions Tutorial. +1 on using different titles. No opinion your particular suggestion, but the TOC on the tutorial needs to be consistent as well. > The avg function is confusingly indexed only as "average", which > shouldn't really be a problem... unless someone types in "avg" into > their browser's find box. Maybe this should have "average" as a > primary term and "avg" as a secondary (with Pavel's 'median" function > to be added later). I think we should have index entries for function names, aggregate or not. Perhaps avgaggregate function ? Hmm, or maybe the other way around, so that all aggregates are listed together in the index? Not sure. (but surely we don't want to have all functions lumped together in a single "function"). For some reason I don't like averageavg, but then I don't like the current average either. > But next to this "average" index entry are links > to both the aggregate function sections, which are named identically. > I raised a similar issue to this for "privileges" in the index > previously. Confusing index entries favor no one. +1 for fixes you can suggest. -- Álvaro Herrera The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support