| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | ispell/hunspell imprecision in error message |
| Date: | 2016-07-25 16:53:31 |
| Message-ID: | 1ae69bcd-2fef-b9d3-41d5-54da05c5d1a6@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2016-07-25 17:46:08 | Re: No longer possible to query catalogs for index capabilities? |
| Previous Message | Andrew Gierth | 2016-07-25 15:02:23 | Re: No longer possible to query catalogs for index capabilities? |