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?

-- 
greg
http://mit.edu/~gsstark/resume.pdf

In response to

• pgsql: Cause pg_proc.probin to be declared as text, not bytea. at 2009-08-04 04:04:12 from Tom Lane

Responses

• Re: [COMMITTERS] pgsql: Cause pg_proc.probin to be declared as text, not bytea. at 2009-08-04 13:46:45 from Tom Lane

pgsql-hackers by date

Next:	From: wader2	Date: 2009-08-04 13:26:35
	Subject: Re: BUG #4961: pg_standby.exe crashes with no args
Previous:	From: Tsutomu Yamada	Date: 2009-08-04 11:03:34
	Subject: Re: Proposal: More portable way to support 64bit platforms

pgsql-committers by date

Next:	From: User Maosen	Date: 2009-08-04 12:03:20
	Subject: pgexternaltable - src:
Previous:	From: Tom Lane	Date: 2009-08-04 04:04:12
	Subject: pgsql: Cause pg_proc.probin to be declared as text, not bytea.