Message-ID: <4E422729.7000007@ringerc.id.au>
Date: Wed, 10 Aug 2011 14:37:29 +0800
From: Craig Ringer <ringerc@ringerc.id.au>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
	rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: c k <shreeseva.learning@gmail.com>
CC: pgsql-general@postgresql.org,
 pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: postgresql server crash on windows 7 when using plpython
References: 
 <CAN2Y=uMs3SwWwogKpazMPKFTbuJZngOhaDLxYg+XReJK=BzpPA@mail.gmail.com>
In-Reply-To: 
 <CAN2Y=uMs3SwWwogKpazMPKFTbuJZngOhaDLxYg+XReJK=BzpPA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 9/08/2011 10:54 PM, c k wrote:

> Normal python functions returning text etc. are working but when conatining
>
> import sys
> from uuid import getnode as get_mac
> mac = get_mac()
> return mac
>
> fails. What will be the reason?

You still haven't supplied the error message you get when you run this.

In the absence of better information, my guess would be that python's 
uuid module uses ossp-uuid, same as PostgreSQL does, but a different 
version or one compiled differently. The PostgreSQL `bin' dir with the 
postgresql version of the DLL will be in the path before the Python one, 
so Python is calling into a different version of the DLL than it expects 
and probably crashing as a result.

That would be consistent with it working from the python command line.

To work around this, I'd either use the ossp-uuid functions via the SPI 
rather than using the Python UUID module, or I'd remove the OSSP-UUID 
dll from the postgresql directory. You can certainly try that to see if 
it helps.

This is one of the joys you get with Windows software not being managed 
by a central packaging system. Everyone bundles their own versions of 
all the dependencies, leaving messes like this where two DLLs with the 
same name aren't quite compatible. Yay!

--
Craig Ringer