Thread: Debian PLPython

Hi Chaps,

I'm still learning, so please be patient.

I recently installed 8.0.0 RC1 on my windows machine. The languages
node (in pgadmin) listed two languages, one being plpython.

I've now installed 7.4 on our debian server, but it appears not to
come with plpython installed. I am unable to find any plpython related
packages to install, however I did find some posts (from around Aug
2003) mentioning that plpython support may be dropped from postgresql.

Is this true, or is the missing language simply a matter of me not
installing the correct packages?

Sw.

Simon Wittber <simonwittber@gmail.com> writes:
> I've now installed 7.4 on our debian server, but it appears not to
> come with plpython installed.

Should be there, though you may need an auxiliary package.  I'm not
sure how Debian splits things up, but in RPM-based distributions it's
in a postgresql-python package.

A couple things to check:
1. It's "plpythonu", not "plpython".
2. Did you do a createlang operation?

            regards, tom lane

Simon Wittber <simonwittber@gmail.com> writes:

> I've now installed 7.4 on our debian server, but it appears not to
> come with plpython installed.

It does to, you should have a files like:

bash-3.00$ ls -l /usr/lib/postgresql/lib/pl*.so
-rw-r--r--  1 root root  32896 Dec  1 04:19 /usr/lib/postgresql/lib/plperl.so
-rw-r--r--  1 root root 114252 Dec  1 04:19 /usr/lib/postgresql/lib/plpgsql.so
-rw-r--r--  1 root root  39780 Dec  1 04:19 /usr/lib/postgresql/lib/plpython.so

You have to su to postgres and run createlang on each database you want to
have the language in though. Something like:

createlang -d databasename plpython

You could do this for the template1 database if you want it to be in all
subsequently created databases. I always find that more confusing in the long
run though.

--
greg

>
> createlang -d databasename plpython
>

excellent, that does the trick. thankyou.

I guess I was confused, as the langauges came 'pre-created' on the 8.0
RC1 windows install.