| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Aidan Van Dyk <aidan(at)highrise(dot)ca>, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, Joel Jacobson <joel(at)trustly(dot)com>, Vik Reykja <vikreykja(at)gmail(dot)com>, Michael Glaesemann <grzm(at)seespotcode(dot)net>, Gurjeet Singh <singh(dot)gurjeet(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Schema version management |
| Date: | 2012-07-10 21:54:28 |
| Message-ID: | 4FFCA494.2020401@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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(at)gmx(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2012-07-10 21:55:09 | Re: Schema version management |
| Previous Message | Dimitri Fontaine | 2012-07-10 21:42:52 | Re: Synchronous Standalone Master Redoux |