| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | 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>, Andrew Dunstan <andrew(at)dunslane(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:39:09 |
| Message-ID: | 1341956349.14340.2.camel@vanquo.pezone.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dimitri Fontaine | 2012-07-10 21:42:52 | Re: Synchronous Standalone Master Redoux |
| Previous Message | Peter Geoghegan | 2012-07-10 21:14:23 | Re: enhanced error fields |