Found the problem. If I have a very long environment variable exported
and I start PG, PG crashes when I try to load PG/Tcl. In my case I use
color ls and I have a very long LS_COLORS environment variable set.
I have duplicated the problem by renaming my .bashrc and logging back
in. With thi
Scott Goodwin <[EMAIL PROTECTED]> writes:
> I'll grab the CVS PG copy and try it out. Is this something the Darwin
> folks should be notified about? It might cause problems with other
> apps.
It's unlikely that they'll consider it their problem.
regards, tom lane
--
I'll grab the CVS PG copy and try it out. Is this something the Darwin
folks should be notified about? It might cause problems with other
apps.
thanks,
/s.
On Feb 22, 2004, at 4:47 PM, Tom Lane wrote:
Scott Goodwin <[EMAIL PROTECTED]> writes:
Found the problem. If I have a very long environme
Scott Goodwin <[EMAIL PROTECTED]> writes:
> Found the problem. If I have a very long environment variable exported
> and I start PG, PG crashes when I try to load PG/Tcl. In my case I use
> color ls and I have a very long LS_COLORS environment variable set.
I was able to duplicate this. I am
I'm certain that the length of a single env var is the only factor
involved, and not the size of the enviroment itself. If I login to my
normal environment and unset LS_COLORS, everything works fine. If I
move my .bashrc out of the way, login fresh and create an env var > 522
chars, it fails. M
Scott Goodwin <[EMAIL PROTECTED]> writes:
> Found the problem. If I have a very long environment variable exported
> and I start PG, PG crashes when I try to load PG/Tcl. In my case I use
> color ls and I have a very long LS_COLORS environment variable set.
Interesting. Did you check whether
Ok, so it's something specific to my setup. I created a test account,
logged in and compiled postgresql there with a clean shell environment
and it worked fine. So I'm shooting myself in the foot in my login
environment. *sigh*.
thanks,
/s.
On Feb 21, 2004, at 1:51 AM, Tom Lane wrote:
Scott
Scott Goodwin <[EMAIL PROTECTED]> writes:
> Hoping someone can help me figure out why I can't get PL/Tcl to load
> without crashing the backend on Mac OS 10.3.2.
FWIW, pltcl seems to work for me. Using up-to-date Darwin 10.3.2
and PG CVS tip, I did
configure --with-tcl --without-tk
then
Hoping someone can help me figure out why I can't get PL/Tcl to load
without crashing the backend on Mac OS 10.3.2.
I compile Tcl, PostgreSQL, create the database and then run the
following:
create function plpgsql_call_handler() RETURNS LANGUAGE_HANDLER
as 'plpgsql.so' language 'c';
create t
