Re: duplicated index entry found ... - Mailing list pgsql-docs

From Peter Eisentraut
Subject Re: duplicated index entry found ...
Date
Msg-id Pine.LNX.4.56.0308051910080.2104@krusty.credativ.de
Whole thread Raw
In response to Re: duplicated index entry found ...  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-docs
Tom Lane writes:

> The Hermit Hacker <scrappy@postgresql.org> writes:
> > duplicated index entry found, CHARACTER STRINGS LENGTH
> > duplicated index entry found, LENGTH CHARACTER STRINGS
> > duplicated index entry found, SUBSTRING
> > duplicated index entry found, SUBSTRING
> > 4 entries ignored...
>
> Yeah, I've been seeing that for quite some time, but haven't been able
> to figure out what it's complaining about.  Surely multiple index
> entries for the same term are legal, so what's its beef?

Since by default (which we don't override) an index entry points to its
nearest containing section (rather than directly to its occurence), if a
section contains the same index entry more than once, it does indeed look
like a duplicate on the outside.  There are at least two obvious ways to
get rid of the warnings, but I could never figure out the benefits and
drawbacks of them.

--
Peter Eisentraut   peter_e@gmx.net

pgsql-docs by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: man pages for v7.4 ... ?
Next
From: "Marc G. Fournier"
Date:
Subject: Testing gateway