Received: from localhost (unknown [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 348239F94CB for ; Mon, 3 Sep 2007 14:03:00 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 87588-01 for ; Mon, 3 Sep 2007 14:02:54 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.231]) by postgresql.org (Postfix) with ESMTP id 994149F94A7 for ; Mon, 3 Sep 2007 14:02:54 -0300 (ADT) Received: by wr-out-0506.google.com with SMTP id 68so674089wri for ; Mon, 03 Sep 2007 10:02:52 -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=TYr1p7CL3qCpinUnViUfXbb+O7IAhpd54KpmCXACe++WtlGh1Fzu+LzR0ROTYwtEbdoqIRN7Ox1DxI+n52aRfKJQYFgyhff8oC5myV74d+vq+f+MkqUJ1hx0pihluJUPv7CbvXzHkkF4c1fkI0MfPUYZZGps8Y42vW1Picyc1yU= 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=jf93MbgVWSvjdKCQk6cNkK8jQQnX/VQsMOLrmYZaME77k2eKucypzztZg4wmAxcF9xPxZipsfsnGjAKtdNosuY6TjzPyQqe6CkNg80tULzUDETueKl7y4nRh82LhTb8OAWOowEhQFvF0pzUOwlwgVAHpQGorlXGxiPKD0gxnEYo= Received: by 10.115.78.1 with SMTP id f1mr3225558wal.1188838970132; Mon, 03 Sep 2007 10:02:50 -0700 (PDT) Received: by 10.114.75.8 with HTTP; Mon, 3 Sep 2007 10:02:49 -0700 (PDT) Message-ID: <90bce5730709031002r58c8f1d8oece7692da0597ba6@mail.gmail.com> Date: Mon, 3 Sep 2007 10:02:50 -0700 From: "Trevor Talbot" To: "Mark Mielke" Subject: Re: tsearch filenames unlikes special symbols and numbers Cc: "Tom Lane" , "Gregory Stark" , "Magnus Hagander" , "Oleg Bartunov" , "Pavel Stehule" , "PostgreSQL Hackers" In-Reply-To: <46DC2024.4010509@mark.mielke.cc> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 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> <87tzqci6tp.fsf@oxford.xeocode.com> <20070903075609.GD21833@svr2.hagander.net> <1692.1188826039@sss.pgh.pa.us> <87zm03zwqs.fsf@oxford.xeocode.com> <8195.1188828543@sss.pgh.pa.us> <46DC2024.4010509@mark.mielke.cc> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200709/94 X-Sequence-Number: 107246 On 9/3/07, Mark Mielke wrote: > Tom Lane wrote: > > Also, ____ says that Windows throws an error for ":" in the filename, > > which means we needn't. > Windows doesn't fail - but it can do odd things. For example, try: > > C:\> echo hi >foo:bar > > If one then checks the directory, one finds a "foo". : is used for naming streams and attribute types in NTFS filenames. It's not very well-known functionality and tends to confuse people, but I'm not aware of any situation where it'd be a problem for read access. (Creation is not a security risk in the technical sense, but as most administrators aren't aware of alternate data streams and the shell does not expose them, it's effectively hidden data.) If any of you are familiar with MacOS HFS resource forks, NTFS basically supports an arbitrary number of named forks. A file is collection of one or more data streams, the single unnamed stream being default.