Re: pltlc and pltlcu problems

after i have succesfully used createlan script to load both the trusted and untrusted tlc languages i try some tests


i create a test function (right out of the docs)


	CREATE FUNCTION tcl_max (int4, int4) RETURNS int4 AS '
	    if {$1 > $2} {return $1}
	    return $2
	' LANGUAGE 'pltclu';



and i try to run this stest

	select tcl_max(4,6);

but i get


	ERROR:  fmgr_info: function 17020: cache lookup failed

so i create trusted version


	CREATE FUNCTION tcl_max (int4, int4) RETURNS int4 AS '
	    if {$1 > $2} {return $1}
	    return $2
	' LANGUAGE 'pltcl';

and i again try to run this stest

	select tcl_max(4,6);

but i get instead

	server closed the connection unexpectedly
	        This probably means the server terminated abnormally
	        before or while processing the request.
	connection to server was lost


and if i look at the log

postgres: murray kale [local] SELECT: error while loading shared libraries: /usr/lib/postgresql/pltcl.so: undefined symbol: Tcl_CreateInterp
DEBUG:  server process (pid 18415) exited with exit code 127
DEBUG:  terminating any other active server processes
DEBUG:  all server processes terminated; reinitializing shared memory and semaphores
DEBUG:  database system was interrupted at 2002-01-19 15:01:29 EST
DEBUG:  checkpoint record is at 0/4BAD10
DEBUG:  redo record is at 0/4BAD10; undo record is at 0/0; shutdown TRUE
DEBUG:  next transaction id: 2120; next oid: 49324
DEBUG:  database system was not properly shut down; automatic recovery in progress
DEBUG:  redo starts at 0/4BAD50
DEBUG:  ReadRecord: record with zero length at 0/4C0FB4
DEBUG:  redo done at 0/4C0F90
DEBUG:  database system is ready


so what do i do now?

log it as a bug?


murray



so ok i go to the sources looking for test of pl/tlc or pl/tlcu (untrusted)





Tom Lane wrote:

>Murray Prior Hobbs <murray@efone.com> writes:
>
>>ERROR:  Load of file /usr/lib/postgresql/pltcl.so failed: 
>>/usr/lib/postgresql/pltcl.so: undefined symbol: pg_get_enconv_by_encoding
>>
>
>Looks like a multibyte-enabled pltcl and a non-multibyte-enabled
>backend.  Given that they were clearly built at different times and
>with different configurations, one might also wonder if they're even
>the same Postgres version.
>
>			regards, tom lane
>
>---------------------------(end of broadcast)---------------------------
>TIP 4: Don't 'kill -9' the postmaster
>