I don't have much experience with Postgres but it seems to me that it is a server configuration issue - perhaps the server startup scripts may not be pulling in the bashrc used by the interactive login, or the pg-python/plpythonu interfaces start Python with separate environments without reference to that bashrc. The fact that pg-python starts a different Python version to plpythonu indicates distinct configuration settings for these.
-------------------------> "These thoughts are mine alone!" <---------
Andrew MacIntyre Operations Branch
tel: +61 2 6219 5356 Communications Infrastructure Division
fax: +61 2 6253 3277 Australian Communications & Media Authority
email: andrew.macintyre@acma.gov.au http://www.acma.gov.au/
-----Original Message-----
Message: 3
Date: Thu, 19 Jul 2012 22:36:41 +1000
From: Mark Wynter <mark@dimensionaledge.com>
To: grass-user@lists.osgeo.org
Subject: Re: [GRASS-user] Problem accessing GRASS from GRASS from
PostgreSQL9.1/PostGIS2.0 via pg-python or plpythonu
Message-ID: <F57CA683-3E5B-49B1-A5FD-
412FA69ED0C1@dimensionaledge.com>
Content-Type: text/plain; charset=us-ascii
{...}
OK, I've got two versions of python: 2.7 and 3.2...
Both python console and postgresql can see python 2.7 but plus it appears
the grass environmental variables are not finding their way into the
$pythonpath as seen by the postgresql server???Any suggestions?
NOTICE: This email message is for the sole use of the intended recipient(s)
and may contain confidential and privileged information. Any unauthorized
review, use, disclosure or distribution is prohibited. If you are not the
intended recipient, please contact the sender by reply email and destroy all
copies of the original message.