Excerpts from Peter Eisentraut's message of mié jul 11 17:03:03 -0400 2012:
>
> On tis, 2012-07-10 at 17:54 -0400, Andrew Dunstan wrote:
> > 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.
>
> Yeah, that's a bummer. Then I guess some escape mechanism would be OK.
> I could imagine an operator < on a custom data type being dumped into a
> file named operator_%3C.sql. Still better than putting them all in one
> file.
>
> Of course, argument types need to be dealt with as well, just like with
> functions (plus prefix/postfix).
operator_!___numeric.sql (postfix, name does not need escape)
operator_%7C%2F_integer__.sql (prefix)
operator_%3C_bit_varying__bit_varying.sql (type name with spaces,
changed to _)
--
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support