To: Alvaro Herrera <alvherre@commandprompt.com>
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: <20070903190302.GD10282@alvh.no-ip.org> 
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>
	<20070903190302.GD10282@alvh.no-ip.org>
Comments: In-reply-to Alvaro Herrera <alvherre@commandprompt.com>
	message dated "Mon, 03 Sep 2007 15:03:02 -0400"
Date: Mon, 03 Sep 2007 15:15:05 -0400
Message-ID: <24214.1188846905@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

Alvaro Herrera <alvherre@commandprompt.com> writes:
> On the other hand, this means the name has to be quoted if it would be
> quoted as an SQL identifier, right?

Something like that.  I wasn't planning on rejecting uppercase letters,
though, which would be necessary if you wanted to be strict about
matching unquoted identifiers.

There seems fairly clear use-case for allowing A-Z a-z 0-9 and
underscore (while CVS head rejects 0-9 and underscore).  There also seem
to be good arguments for disallowing / \ : on various platforms, which
leaves us with some other punctuation in question, as well as the whole
matter of non-ASCII characters.  I'm not sure whether we want to touch
the idea of non-ASCII; comments?

			regards, tom lane