ispell/hunspell imprecision in error message - Mailing list pgsql-hackers

From Peter Eisentraut
Subject ispell/hunspell imprecision in error message
Date
Msg-id 1ae69bcd-2fef-b9d3-41d5-54da05c5d1a6@2ndquadrant.com
Whole thread Raw
Responses Re: ispell/hunspell imprecision in error message  (Artur Zakirov <a.zakirov@postgrespro.ru>)
List pgsql-hackers
I was trying to look up the background of this error message:

"Ispell dictionary supports only \"default\", \"long\", and \"num\" flag
value"

(src/backend/tsearch/spell.c)

But I found that this actually talks about Hunspell format dictionaries.(So the man page is hunspell(5) as opposed to
ispell(5).) While as far
 
as the tsearch interfaces are concerned, those two are lumped together,
should we not change the error message to refer to Hunspell?

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Andrew Gierth
Date:
Subject: Re: No longer possible to query catalogs for index capabilities?
Next
From: Robert Haas
Date:
Subject: Re: No longer possible to query catalogs for index capabilities?