| From: | Greg Stark <gsstark(at)mit(dot)edu> |
|---|---|
| To: | Tom Lane <tgl(at)postgresql(dot)org> |
| Cc: | pgsql-committers(at)postgresql(dot)org |
| Subject: | Re: pgsql: Cause pg_proc.probin to be declared as text, not bytea. |
| Date: | 2009-08-04 11:33:23 |
| Message-ID: | 407d949e0908040433u33993824q1d8825e3ebc4ced3@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Tue, Aug 4, 2009 at 5:04 AM, Tom Lane<tgl(at)postgresql(dot)org> wrote:
> Cause pg_proc.probin to be declared as text, not bytea.
Doesn't this relate to the earlier discussion of whether to re-encode
filenames and paths?
What's going to happen if I have filenames which aren't valid encoded
strings in the server encoding -- say UTF8 filenames but I'm using
latin1 in the server or vice versa. Will my CREATE FUNCTION command
end up storing an invalid encoded string? Or re-encode the filename
and then fail to find the file?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | User Maosen | 2009-08-04 12:03:20 | pgexternaltable - src: |
| Previous Message | Tom Lane | 2009-08-04 04:04:12 | pgsql: Cause pg_proc.probin to be declared as text, not bytea. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | wader2 | 2009-08-04 13:26:35 | Re: BUG #4961: pg_standby.exe crashes with no args |
| Previous Message | Tsutomu Yamada | 2009-08-04 11:03:34 | Re: Proposal: More portable way to support 64bit platforms |