pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Pavel Stehule <pavel.stehule@gmail.com>
Cc: Ben Tilly <btilly@gmail.com>
Cc: Alvaro Herrera <alvherre@commandprompt.com>
Cc: Gregory Stark <stark@enterprisedb.com>
Cc: Oleg Bartunov <oleg@sai.msu.su>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Subject: Re: tsearch filenames unlikes special symbols and numbers
Date: Tue, 04 Sep 2007 09:53:01 -0400
Message-ID: <23999.1188913981@sss.pgh.pa.us> (raw)
In-Reply-To: <162867790709032204m1895d36ci78de7d4f4e759655@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>
	<5404.1188864206@sss.pgh.pa.us>
	<162867790709032204m1895d36ci78de7d4f4e759655@mail.gmail.com>

"Pavel Stehule" <pavel.stehule@gmail.com> writes:
> 2007/9/4, Tom Lane <tgl@sss.pgh.pa.us>:
>> 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 ...

> 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.

You're going to need to alter that habit anyway, because it's not
appropriate to mention any specific encoding in the dictionary name.

But on further thought it strikes me that insisting on all lower case
doesn't eliminate case-sensitivity portability problems.  For instance,
suppose the given parameter is 'foo' and the actual file name is
Foo.dict.  This will work fine on Windows and will stop working when
moved to Unix.  So I'm not sure we really buy much by rejecting
upper-case letters in the parameter --- all we do is constrain which
side of the fence you have to fix any mismatches on.  And we picked the
side that only a DBA, rather than a plain SQL user, can fix.

			regards, tom lane



view thread (31+ messages)  latest in thread

Message-ID: <23999.1188913981@sss.pgh.pa.us>
Permalink:  ../23999.1188913981@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/23999.1188913981@sss.pgh.pa.us

 · 

reply

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, pavel.stehule@gmail.com, btilly@gmail.com, alvherre@commandprompt.com, stark@enterprisedb.com, oleg@sai.msu.su, pgsql-hackers@postgresql.org
  Subject: Re: tsearch filenames unlikes special symbols and numbers
  In-Reply-To: <23999.1188913981@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