Received: from localhost (unknown [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 4207B9F9C16 for ; Tue, 4 Sep 2007 02:08:24 -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 72842-06-2 for ; Tue, 4 Sep 2007 02:08:17 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.231]) by postgresql.org (Postfix) with ESMTP id 6AEFE9F9F9A for ; Tue, 4 Sep 2007 02:04:28 -0300 (ADT) Received: by wx-out-0506.google.com with SMTP id r21so1558305wxc for ; Mon, 03 Sep 2007 22:04:27 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=lEkp0xZOYAxwObb4I52n3ENpVtpas6tBAhvyTnnXwzIHYejNS2EYKJ87sBxNHhIceItjY9gVRLN3oHvEfmqLn268ipH5UcdhcR3hKd0qAP24Bd5VC9eZR7+ovejB+1zRRluQlE6ASu/RMh4H/yb3r/By5MsOtZ3+7Kgdt9UwKFw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=sgMtRU09SIRRbTinQbQWLJur4J979io+tjUirwMWlLgdgO/7Fej3d3E0/roR+eONn+Jpwb2nIiCLmyF8ZgVUnkbBTM3iOZsnX7Ee9sKyrvG4pP8LHYOV4zqUKUffhQ3iRPXV7skaK8/tXf1jPBhyUPMZcvxuyChPRnwSRRYPuWo= Received: by 10.90.83.14 with SMTP id g14mr4570374agb.1188882267713; Mon, 03 Sep 2007 22:04:27 -0700 (PDT) Received: by 10.90.34.18 with HTTP; Mon, 3 Sep 2007 22:04:27 -0700 (PDT) Message-ID: <162867790709032204m1895d36ci78de7d4f4e759655@mail.gmail.com> Date: Tue, 4 Sep 2007 07:04:27 +0200 From: "Pavel Stehule" To: "Tom Lane" Subject: Re: tsearch filenames unlikes special symbols and numbers Cc: "Ben Tilly" , "Alvaro Herrera" , "Gregory Stark" , "Oleg Bartunov" , "PostgreSQL Hackers" In-Reply-To: <5404.1188864206@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <162867790709021328i7771aa9jfe79268bccbf123d@mail.gmail.com> <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> <5404.1188864206@sss.pgh.pa.us> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200709/121 X-Sequence-Number: 107273 2007/9/4, Tom Lane : > "Ben Tilly" writes: > > On 9/3/07, Tom Lane 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 > It's system specific. I prefere a-z and A-Z. Clasic name for dictionaries combine lower and upper characters .. for czech cs_CZ_UTF8 etc. dictfile = cs_CZ_UTF8 ... automatic convert to cs_cz_utf8.dict dictfile = 'cs_CZ_UTF8' .. check and use cs_CZ_UTF8 Regards Pavel Stehule p.s. it's important on UNIX platforms and without any efect on windows.