Greg Stark wrote:
> On Tue, Aug 4, 2009 at 2:46 PM, Tom Lane<tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> I'll point out though that having probin declared bytea would surely
>> be antithetical to any attempt to treat shlib filenames in an
>> encoding-aware fashion. Declaring it that way implies that it is
>> *not* storing a character string that has any particular encoding.
> Well that's kind of the point. Unix filesystems traditionally prohibit
> '/' and '\0' but otherwise allowing any series of bytes without
> requiring any particular encoding. If we used bytea to store
> filesystem paths then you could specify any arbitrary series of bytes
> without worrying that the server will re-encode it differently.
Is this any different from the path in "COPY foo to '/path/to/file'"?
I suspect the probin stuff is a solution in search of a problem.
In response to
pgsql-hackers by date
|Next:||From: Sam Mason||Date: 2009-08-04 15:03:40|
|Subject: Re: Review: Revise parallel pg_restore's scheduling heuristic|
|Previous:||From: Pavel Stehule||Date: 2009-08-04 14:58:22|
|Subject: Re: pg_proc.probin should become text?|
pgsql-committers by date
|Next:||From: Tom Lane||Date: 2009-08-04 15:37:02|
|Subject: Re: Re: [COMMITTERS] pgsql: Cause pg_proc.probin to be declared as text, not bytea. |
|Previous:||From: Greg Stark||Date: 2009-08-04 14:42:34|
|Subject: Re: [COMMITTERS] pgsql: Cause pg_proc.probin to be declared as text, not bytea.|