Text search dictionary vs. the C locale

From: twoflower <standa(dot)kurik(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Text search dictionary vs. the C locale
Date: 2017-07-02 11:35:24
Message-ID: 1498995324472-5969677.post@n3.nabble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I am having problems creating an Ispell-based text search dictionary for
Czech language.

Issuing the following command:

create text search dictionary czech_ispell (
&nbsp;&nbsp;template = ispell,
&nbsp;&nbsp;dictfile = czech_ispell,
&nbsp;&nbsp;affFile = czech_ispell
);

ends with

ERROR: syntax error
CONTEXT: line 252 of configuration file
"/usr/share/postgresql/9.6/tsearch_data/czech_ispell.affix": " . > TŘIA

The dictionary files are in UTF-8. The database cluster was initialized with

initdb --locale=C --encoding=UTF8

When, on the other hand, I initialize it with

initdb --locale=en_US.UTF8

it works.

I was hoping I could have the C locale with the UTF-8 encoding but it seems
non-ASCII text search dictionaries are not supported in that case. This is a
shame as restoring the dumps goes from 1.5 hour (with the C locale) to 9.5
hours (with en_US.UTF8).

--
View this message in context: http://www.postgresql-archive.org/Text-search-dictionary-vs-the-C-locale-tp5969677.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.

Responses

Browse pgsql-general by date

  From Date Subject
Next Message twoflower 2017-07-02 13:11:07 Re: Text search dictionary vs. the C locale
Previous Message rajan 2017-07-02 06:31:22 Need help on compiling postgres source code from cloned repo