Re: Re: [COMMITTERS] pgsql: Cause pg_proc.probin to be declared as text, not bytea.
От | Andrew Dunstan |
---|---|
Тема | Re: Re: [COMMITTERS] pgsql: Cause pg_proc.probin to be declared as text, not bytea. |
Дата | |
Msg-id | 4A784D21.7000806@dunslane.net обсуждение исходный текст |
Ответ на | Re: [COMMITTERS] pgsql: Cause pg_proc.probin to be declared as text, not bytea. (Greg Stark <gsstark@mit.edu>) |
Ответы |
Re: Re: [COMMITTERS] pgsql: Cause pg_proc.probin to be declared as text, not bytea.
|
Список | pgsql-hackers |
Greg Stark wrote: > On Tue, Aug 4, 2009 at 2:46 PM, Tom Lane<tgl@sss.pgh.pa.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. cheers andrew
В списке pgsql-hackers по дате отправления: