Re: Re: [COMMITTERS] pgsql: Cause pg_proc.probin to be declared as text, not bytea. - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Re: [COMMITTERS] pgsql: Cause pg_proc.probin to be declared as text, not bytea.
Date
Msg-id 24868.1249400222@sss.pgh.pa.us
Whole thread Raw
In response to Re: Re: [COMMITTERS] pgsql: Cause pg_proc.probin to be declared as text, not bytea.  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes:
> 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.

Well, the previous probin behavior is demonstrably broken.  Make a shlib
with backslash or non-ASCII in the name, create a function referencing
it, dump and reload.  Whatever your opinions are about encodings, you
won't think pg_dump did the right thing.

I'm not sure whether the more general pathname encoding issue is worth
working on or not.  In general it's a non-problem if the paths in the
server filesystem are written in the database encoding.  If they are
not, then you have to figure out what they *are* written in, and that
seems a bit tough.  But anyway that problem is hardly restricted to
probin, and a solution that works only for probin doesn't seem terribly
interesting.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Alpha Releases: Docs?
Next
From: Tom Lane
Date:
Subject: Re: Proposal: More portable way to support 64bit platforms