Received: from localhost (unknown [200.46.204.182])
	by postgresql.org (Postfix) with ESMTP id EAA479F96D0
	for <pgsql-hackers-postgresql.org@postgresql.org>;
	Mon,  3 Sep 2007 21:03:47 -0300 (ADT)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024)
	with ESMTP id 16591-04 for
	<pgsql-hackers-postgresql.org@postgresql.org>;
	Mon,  3 Sep 2007 21:03:38 -0300 (ADT)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.5
Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130])
	by postgresql.org (Postfix) with ESMTP id 5B4D89F963F
	for <pgsql-hackers@postgresql.org>;
	Mon,  3 Sep 2007 21:03:44 -0300 (ADT)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id l8403QdH005405;
	Mon, 3 Sep 2007 20:03:26 -0400 (EDT)
To: "Ben Tilly" <btilly@gmail.com>
cc: "Alvaro Herrera" <alvherre@commandprompt.com>,
	"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: <acc274b30709031650i5b10de96se8168c6ea27a1a4f@mail.gmail.com> 
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>
	<24214.1188846905@sss.pgh.pa.us>
	<acc274b30709031650i5b10de96se8168c6ea27a1a4f@mail.gmail.com>
Comments: In-reply-to "Ben Tilly" <btilly@gmail.com>
	message dated "Mon, 03 Sep 2007 16:50:03 -0700"
Date: Mon, 03 Sep 2007 20:03:26 -0400
Message-ID: <5404.1188864206@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200709/112
X-Sequence-Number: 107264

"Ben Tilly" <btilly@gmail.com> writes:
> On 9/3/07, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> There seems fairly clear use-case for allowing A-Z a-z 0-9 and
>> underscore (while CVS head rejects 0-9 and underscore).

> The problem with allowing uppercase letters is that on some
> filesystems foo and Foo are the same file, and on others they are not.
>  This may lead to obscure portability problems where code worked fine
> on Unix and then fails when the database is running on Windows.

Yeah, good point.  So far it seems that a-z 0-9 and underscore cover the
real use-cases, so what say we just allow those for now?  It's a lot
easier to loosen up later than tighten up ...

			regards, tom lane