pg.ddx.io pgsql-docs@postgresql.org mailing list archive
help / color / mirror / Atom feedduplicated index entry found ...
3+ messages / 3 participants
[nested] [flat]
* duplicated index entry found ...
@ 2003-08-05 04:29 The Hermit Hacker <scrappy@postgresql.org>
0 siblings, 1 reply; 3+ messages in thread
From: The Hermit Hacker @ 2003-08-05 04:29 UTC (permalink / raw)
To: pgsql-docs
Non-critical, but figured I'd mention it ... this was from the beta build
this evening ...
/usr/local/bin/perl /usr/local/share/sgml/docbook/dsssl/modular/bin/collateindex.pl -f -g -i 'bookindex' -o bookindex.sgml HTML.index
Processing HTML.index...
568 entries loaded...
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...
Done.
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: duplicated index entry found ...
@ 2003-08-05 14:02 Tom Lane <tgl@sss.pgh.pa.us>
parent: The Hermit Hacker <scrappy@postgresql.org>
0 siblings, 1 reply; 3+ messages in thread
From: Tom Lane @ 2003-08-05 14:02 UTC (permalink / raw)
To: The Hermit Hacker <scrappy@postgresql.org>; +Cc: pgsql-docs
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?
regards, tom lane
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: duplicated index entry found ...
@ 2003-08-05 17:13 Peter Eisentraut <peter_e@gmx.net>
parent: Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 0 replies; 3+ messages in thread
From: Peter Eisentraut @ 2003-08-05 17:13 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: The Hermit Hacker <scrappy@postgresql.org>; 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
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2003-08-05 17:13 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2003-08-05 04:29 duplicated index entry found ... The Hermit Hacker <scrappy@postgresql.org>
2003-08-05 14:02 ` Tom Lane <tgl@sss.pgh.pa.us>
2003-08-05 17:13 ` Peter Eisentraut <peter_e@gmx.net>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox