Re: [COMMITTERS] pgsql: Cause pg_proc.probin to be declared as text, not bytea.

Поиск
Список
Период
Сортировка
От Greg Stark
Тема Re: [COMMITTERS] pgsql: Cause pg_proc.probin to be declared as text, not bytea.
Дата
Msg-id 407d949e0908040742i7d8b84f7x6fefbe200eed63b2@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [COMMITTERS] pgsql: Cause pg_proc.probin to be declared as text, not bytea.  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Re: [COMMITTERS] pgsql: Cause pg_proc.probin to be declared as text, not bytea.  (Andrew Dunstan <andrew@dunslane.net>)
Список pgsql-hackers
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
byteswithout 
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


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: bytea vs. pg_dump
Следующее
От: Alvaro Herrera
Дата:
Сообщение: Re: pg_proc.probin should become text?