From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Greg Stark <gsstark(at)mit(dot)edu> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Re: [COMMITTERS] pgsql: Cause pg_proc.probin to be declared as text, not bytea. |
Date: | 2009-08-04 15:00:49 |
Message-ID: | 4A784D21.7000806@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
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.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-08-04 15:37:02 | Re: Re: [COMMITTERS] pgsql: Cause pg_proc.probin to be declared as text, not bytea. |
Previous Message | Greg Stark | 2009-08-04 14:42:34 | Re: [COMMITTERS] pgsql: Cause pg_proc.probin to be declared as text, not bytea. |
From | Date | Subject | |
---|---|---|---|
Next Message | Sam Mason | 2009-08-04 15:03:40 | Re: Review: Revise parallel pg_restore's scheduling heuristic |
Previous Message | Pavel Stehule | 2009-08-04 14:58:22 | Re: pg_proc.probin should become text? |