From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Oleg Bartunov" <oleg(at)sai(dot)msu(dot)su>, "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com>, "PostgreSQL Hackers" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: tsearch filenames unlikes special symbols and numbers |
Date: | 2007-09-02 23:26:46 |
Message-ID: | 87y7foir7t.fsf@oxford.xeocode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-hackers |
"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> writes:
>> postgres=# CREATE TEXT SEARCH DICTIONARY ru_ispell (
>> TEMPLATE = ispell,
>> DictFile = 'russian-utf8.dict',
>> AffFile = 'russian-utf8.aff',
>> StopWords = russian
>> );
>> ERROR: invalid text search configuration file name "russian-utf8.dict"
>
> I made it reject all but latin letters, which is the same restriction
> that's in place for timezone set filenames. That might be overly
> strong, but we definitely have to forbid "." and "/" (and "\" on
> Windows). Do we want to restrict it to letters, digits, underscore?
> Or does it need to be weaker than that?
What's the problem with "."?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-09-02 23:51:50 | Re: tsearch filenames unlikes special symbols and numbers |
Previous Message | Tom Lane | 2007-09-02 22:46:11 | Re: tsearch filenames unlikes special symbols and numbers |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-09-02 23:51:50 | Re: tsearch filenames unlikes special symbols and numbers |
Previous Message | Alvaro Herrera | 2007-09-02 22:49:57 | Re: Re: [COMMITTERS] pgsql: Fix brain fade in DefineIndex(): it was continuing to access the |