Re: tsearch filenames unlikes special symbols and numbers - Mailing list pgsql-hackers

From Trevor Talbot
Subject Re: tsearch filenames unlikes special symbols and numbers
Date
Msg-id 90bce5730709030026j6b055e0j453dd691ab139eee@mail.gmail.com
Whole thread Raw
In response to Re: tsearch filenames unlikes special symbols and numbers  (Gregory Stark <stark@enterprisedb.com>)
List pgsql-hackers
On 9/2/07, Gregory Stark <stark@enterprisedb.com> wrote:

> Right, traditionally the only characters forbidden in filenames in Unix are /
> and nul. If we want the files to play nice in Gnome etc then we should
> restrict them to ascii since we don't know what encoding the gui expects.
>
> Actually I think in Windows \ : and . are problems (not allowed more than one
> dot in dos).

Reserved characters in Windows filenames are < > : " / \ | ? *
DOS limitations aren't relevant on the OS versions Postgres supports.

...but I thought this was about opening existing files, not creating
them, in which case the only relevant limitation is path separators.
Any other reserved characters are going to result in no open file,
rather than a security hole.


pgsql-hackers by date:

Previous
From: "Pavel Stehule"
Date:
Subject: integrated tsearch has different results than tsearch2
Next
From: Magnus Hagander
Date:
Subject: Re: [pgsql-www] \dF wrt text search