On 07/10/2012 05:39 PM, Peter Eisentraut wrote:
> On sön, 2012-07-08 at 18:52 -0400, Tom Lane wrote:
>> Peter Eisentraut <peter_e@gmx.net> writes:
>>> On lör, 2012-07-07 at 17:18 -0400, Tom Lane wrote:
>>>> Sure. You need not look further than "/" to find an operator name
>> that
>>>> absolutely *will* cause trouble if it's dumped into a filename
>>>> literally.
>>> But that problem applies to all object names.
>> In principle, yes, but in practice it's far more likely that operators
>> will have names requiring some sort of encoding than that objects with
>> SQL-identifier names will.
> I'm not sure. The only character that's certainly an issue is "/". Are
> there any others on file systems that we want to support?
>
>
In general, NTFS forbids the use of these printable ASCII chars in
filenames (see
<http://en.wikipedia.org/wiki/Filename#Comparison_of_filename_limitations>:
" * : < > ? \ / |
Many of these could be used in operators.
cheers
andrew