Re: pgsql: Cause pg_proc.probin to be declared as text, not bytea. - Mailing list pgsql-committers

From Greg Stark
Subject Re: pgsql: Cause pg_proc.probin to be declared as text, not bytea.
Date
Msg-id 407d949e0908040433u33993824q1d8825e3ebc4ced3@mail.gmail.com
Whole thread Raw
In response to pgsql: Cause pg_proc.probin to be declared as text, not bytea.  (tgl@postgresql.org (Tom Lane))
List pgsql-committers
On Tue, Aug 4, 2009 at 5:04 AM, Tom Lane<tgl@postgresql.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

pgsql-committers by date:

Previous
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Cause pg_proc.probin to be declared as text, not bytea.
Next
From: maosen@pgfoundry.org (User Maosen)
Date:
Subject: pgexternaltable - src: