Date: Thu, 24 Apr 2008 10:12:35 -0400
From: Alvaro Herrera <alvherre@commandprompt.com>
To: alexander lunyov <lan@zato.ru>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: Exceeded maximum lock level
Message-ID: <20080424141235.GE5593@alvh.no-ip.org>
References: <480F46B4.5080102@zato.ru> <20080423145510.GA6572@alvh.no-ip.org>
	<48101BDB.6080501@zato.ru>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <48101BDB.6080501@zato.ru>
User-Agent: Mutt/1.5.17+20080114 (2008-01-14)

alexander lunyov wrote:
> Alvaro Herrera wrote:
>>>  Fatal error 'Exceeded maximum lock level' at line 519 in file   
>>> /usr/src/lib/libpthread/thread/thr_mutex.c (errno = 844913743)
>>
>> This is clearly not a PG problem -- I'd think there's a bug in your own
>> code.
>
> This is very helpful :)
>
> My code is just this:

> I didn't touch any mutex (i don't even sure about what is mutex). While  
> not calling any of sql functions, application works just fine. In  
> non-threaded mode it is working with sql functions. Where did i go wrong?

Well, there are still many things left out, like how many times you call
this function before it fails.  Even then, I suspect the bug is in the
pthread code that comes with your operating system -- or perhaps on the
patches that the port applies to Postgres.

(For the record, I filled the missing pieces in your program and made
SQLLog loop 100000 times, which it did without a hitch.  Next time,
please submit a complete program, not just pieces of it.)

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.