Re: duplicate "median" entry in doc

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: duplicate "median" entry in doc
Date: 2017-02-16 16:06:03
Message-ID: alpine.DEB.2.20.1702161637300.5445@lancre
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


>> When trying to build the documentation there is a minor warning:
>> collateindex.pl: duplicated index entry found: MEDIAN
>
> See
> https://www.postgresql.org/message-id/29262.1483053514@sss.pgh.pa.us
>
> I've been waiting for some clarification on that before attempting
> to fix this. In any case, your proposed patch would remove the main
> index entry, which doesn't seem like what we want.

Hmmm. I do not get it.

I confirm that "oldhtml" does not generate the "see also" in head,
probably because the first termindex/primary is kept and overrides the
second somehow, which is consistent with the warning.

However, after removing the duplicate, both "oldhtml" (openjade 1.3,
issues with 1.4) and "html" (xsltproc) generate a correct "median" index
with its "see also" subsection, in "bookindex.html":

...
MD5, Password Authentication
median, Aggregate Expressions
(see also percentile)
memory context
...

So this really seems ok to me... The only difference is that with the new
chain the percentile is a link and there are parentheses, while with
oldhtml it is just text.

Am I missing something?

--
Fabien.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2017-02-16 16:17:43 Re: Partitioning vs ON CONFLICT
Previous Message Devrim Gündüz 2017-02-16 16:01:48 Re: drop support for Python 2.3