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.

-- 
greg
http://mit.edu/~gsstark/resume.pdf

In response to

• Re: [COMMITTERS] pgsql: Cause pg_proc.probin to be declared as text, not bytea. at 2009-08-04 13:46:45 from Tom Lane

Responses

• Re: Re: [COMMITTERS] pgsql: Cause pg_proc.probin to be declared as text, not bytea. at 2009-08-04 15:00:49 from Andrew Dunstan

pgsql-hackers by date

Next:	From: Tom Lane	Date: 2009-08-04 14:45:52
	Subject: Re: Review: Revise parallel pg_restore's scheduling heuristic
Previous:	From: Tom Lane	Date: 2009-08-04 14:41:25
	Subject: Re: bytea vs. pg_dump

pgsql-committers by date

Next:	From: Andrew Dunstan	Date: 2009-08-04 15:00:49
	Subject: Re: Re: [COMMITTERS] pgsql: Cause pg_proc.probin to be declared as text, not bytea.
Previous:	From: Tom Lane	Date: 2009-08-04 13:46:45
	Subject: Re: [COMMITTERS] pgsql: Cause pg_proc.probin to be declared as text, not bytea.