To: Magnus Hagander <magnus@hagander.net>
cc: Gregory Stark <stark@enterprisedb.com>, Oleg Bartunov <oleg@sai.msu.su>,
	Pavel Stehule <pavel.stehule@gmail.com>,
	PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Subject: Re: tsearch filenames unlikes special symbols and numbers 
In-reply-to: <20070903075609.GD21833@svr2.hagander.net> 
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>
	<87tzqci6tp.fsf@oxford.xeocode.com>
	<20070903075609.GD21833@svr2.hagander.net>
Comments: In-reply-to Magnus Hagander <magnus@hagander.net>
	message dated "Mon, 03 Sep 2007 09:56:09 +0200"
Date: Mon, 03 Sep 2007 09:27:19 -0400
Message-ID: <1692.1188826039@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

Magnus Hagander <magnus@hagander.net> writes:
> On Mon, Sep 03, 2007 at 07:47:14AM +0100, Gregory Stark wrote:
>> Actually I think in Windows \ : and . are problems (not allowed more
>> than one dot in dos).

> \ and : are problems.

Is : really a problem, given that the name in question will be appended
to a known directory's path?

> . is not a problem. We don't support 16-bit windows anyway, and multiple
> dots works fine on any system we support.

I'm not convinced that . is issue-free.  On most if not all versions of Unix,
you are allowed to open a directory as a file and read the filenames it
contains.  While I don't say it'd be easy to manage that through
tsearch, there's at least a potential for discovering the filenames
present in . and .. --- how much do we care about that?

			regards, tom lane