| From: | Greg Stark <gsstark(at)mit(dot)edu> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [COMMITTERS] pgsql: Cause pg_proc.probin to be declared as text, not bytea. |
| Date: | 2009-08-04 14:42:34 |
| Message-ID: | 407d949e0908040742i7d8b84f7x6fefbe200eed63b2@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2009-08-04 15:00:49 | Re: Re: [COMMITTERS] pgsql: Cause pg_proc.probin to be declared as text, not bytea. |
| Previous Message | Tom Lane | 2009-08-04 13:46:45 | Re: [COMMITTERS] pgsql: Cause pg_proc.probin to be declared as text, not bytea. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-08-04 14:45:52 | Re: Review: Revise parallel pg_restore's scheduling heuristic |
| Previous Message | Tom Lane | 2009-08-04 14:41:25 | Re: bytea vs. pg_dump |