Re: [HACKERS] PlPython

From: Hannu Krosing <hannu(at)tm(dot)ee>
To: elein(at)varlena(dot)com
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Kevin Jacobs <jacobs(at)penguin(dot)theopalgroup(dot)com>, pgsql-hackers(at)postgresql(dot)org, pgsql-general(at)postgresql(dot)org
Subject: Re: [HACKERS] PlPython
Date: 2003-07-01 07:23:58
Message-ID: 1057044237.5670.16.camel@fuji.krosing.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

elein kirjutas T, 24.06.2003 kell 00:42:

There is a realtively clean hack one can use to convert plpython
functions to plpythonu manually - just rename the language for the time
of loading functions - do as superuser

update pg_language set lanname = 'plpython' where lanname = 'plpythonu';

LOAD YOUR Pl/Python FUNCTIONS ;

update pg_language set lanname = 'plpythonu' where lanname = 'plpython';

> PS: I've built and tested the plpython patch against
> 7.3.2 and am happy it does not affect the features I count
> on.

As it should.

The untrusted language gives you *more* power, not less.

The untrusted status means that the user has to be trusted to use that
much power.

----------------
Hannu

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Rudy Koento 2003-07-01 09:35:48 updating data but the constraint is set "immediate"
Previous Message Arguile 2003-07-01 05:21:14 Re: 2 different versions of postgres on the same system

Browse pgsql-hackers by date

  From Date Subject
Next Message Christopher Kings-Lynne 2003-07-01 07:44:41 vacuum bug
Previous Message Shridhar Daithankar 2003-07-01 06:56:42 Re: [HACKERS] dblink for Oracle - question ...