I am not going to do stack trace right now, because I am using wireless broadband and is much costlier to download.
But as other functions are working, may be it is related with other thing.
I have forgotten to told that I am using virtual machine for windows. For even this the normal python interpreter does not have any problems. So it seems that the problem is occurring due to crash in python package.
Chaitanya Kulkarni
On Thu, Aug 11, 2011 at 5:37 AM, Craig Ringer
<ringerc@ringerc.id.au> wrote:
On 11/08/2011 1:00 AM, c k wrote:
I have renamed uuid-ossp.dll to 0uuid-ossp.dll in postgresql's lib
directory. But it is also found that postgresql's bin directory is not
included in the path.
Then started the postgresql again, called the same plpython function
again and again server crashed without any details in the log.
Also searched for the above dll or similar in python's installation but
not founf, one available was not dll but was .py file.
Recent log contains following lines.
*Fatal Python error: PyThreadState_Get: no current thread*
Hmm, that's interesting. Thanks for supplying the error message; looks like I was probably on entirely the wrong track because I was forced to guess with not enough information.
If I get a chance I'll have a play with the function you posted and see if I can reproduce the crash on my Win7 box.
In the mean time, if you want you can try to collect some more information about the crash according to these instructions:
http://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Windows
--
Craig Ringer