And, make sure you create the plpythonu language not plpython3u.
--
Thanks & Regards,
Ashesh Vashi
EnterpriseDB INDIA: Enterprise PostgreSQL Company<http://www.enterprisedb.com>
*http://www.linkedin.com/in/asheshvashi*<http://www.linkedin.com/in/asheshvashi>
On Thu, Jan 6, 2011 at 8:46 PM, Ashesh Vashi
<ashesh.vashi@enterprisedb.com>wrote:
> This warning will be there for any dlls.
> So - you can ignore them.
>
> If you have renamed the plpython.dll to plpython3.dll, then please revert
> it back to original one.
> And, then try to create the language.
>
>
> --
> Thanks & Regards,
>
> Ashesh Vashi
> EnterpriseDB INDIA: Enterprise PostgreSQL Company<http://www.enterprisedb.com>
>
>
>
> *http://www.linkedin.com/in/asheshvashi*<http://www.linkedin.com/in/asheshvashi>
>
>
> On Thu, Jan 6, 2011 at 8:42 PM, areveille <areveille@mobigis.fr> wrote:
>
>>
>> Hi,
>>
>> I used dependency walker in order to see which dependencies could be
>> unsatified in plpython.dll and indeed some of them were missing :
>> - python26.dll (I had python2.7 installed but obviously it requires 2.6.)
>> - some .dll that are in the bin folder of posgreSQL
>>
>> So I installed python 2.6 and copy/paste the other missing dlls
>>
>> In the end, when I use dependency walker, plpython.dll still have a
>> warning
>> :
>> "Warning: At least one module has an unresolved import due to a missing
>> export function in a delay-load dependent module."
>> Here is a screen shot of the result in dependency walker :
>> http://postgresql.1045698.n5.nabble.com/file/n3330551/depWalker.png
>> depWalker.png
>>
>> I still can't create the language.
>>
>> Thanks,
>>
>> Alban.
>> --
>> View this message in context:
>> http://postgresql.1045698.n5.nabble.com/BUG-5641-Can-not-create-any-python-language-tp2801518p3330551.html
>> Sent from the PostgreSQL - bugs mailing list archive at Nabble.com.
>>
>> --
>> Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
>> To make changes to your subscription:
>> http://www.postgresql.org/mailpref/pgsql-bugs
>>
>
>
