From: Tom Lane <tgl@sss.pgh.pa.us>
To: Oleg Bartunov <oleg@sai.msu.su>
Cc: Gregory Stark <stark@enterprisedb.com>
Cc: Pavel Stehule <pavel.stehule@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Subject: Re: tsearch filenames unlikes special symbols and numbers
Date: Sun, 09 Sep 2007 11:10:40 -0400
Message-ID: <18346.1189350640@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.LNX.4.64.0709090817530.2767@sn.sai.msu.ru>
References: <162867790709021328i7771aa9jfe79268bccbf123d@mail.gmail.com>
<Pine.LNX.4.64.0709030113090.2767@sn.sai.msu.ru>
<18259.1188773171@sss.pgh.pa.us>
<87y7foir7t.fsf@oxford.xeocode.com>
<19257.1188777110@sss.pgh.pa.us>
<Pine.LNX.4.64.0709090817530.2767@sn.sai.msu.ru>
Oleg Bartunov <oleg@sai.msu.su> writes:
> Oh, my god, I see we dictate extensions !
> Folk, this is too much ! Now, we dictate extensions '.dict, .affix, .stop',
> what else ?
> Does it defined by ispell template only, or it's global requirements ?
It's the callers of get_tsearch_config_filename() that specify the
extension, so AFAICS each dictionary can do what it wants. I don't see
the problem with enforcing an extension: it keeps the namespaces for
different kinds of files separate, and it gets us out of the potential
security risk of allowing access to "." or "..".
I remain of the opinion that we don't really want the SQL-command
definitions of dictionaries to expose the fact that these are files at
all. We should be thinking of the command parameters as identifiers.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: tgl@sss.pgh.pa.us, oleg@sai.msu.su, stark@enterprisedb.com, pavel.stehule@gmail.com, pgsql-hackers@postgresql.org
Subject: Re: tsearch filenames unlikes special symbols and numbers
In-Reply-To: <18346.1189350640@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
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