Skip site navigation (1) Skip section navigation (2)

Re: Exceeded maximum lock level

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: alexander lunyov <lan(at)zato(dot)ru>
Cc: pgsql-interfaces(at)postgresql(dot)org
Subject: Re: Exceeded maximum lock level
Date: 2008-04-24 14:12:35
Message-ID: 20080424141235.GE5593@alvh.no-ip.org (view raw or flat)
Thread:
Lists: pgsql-interfaces
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.

In response to

pgsql-interfaces by date

Next:From: Premil AgarwalDate: 2008-04-29 16:34:05
Subject: VC++ 6: VB6 - Migrate Access database (DAO + JET) to PostgreSQL
Previous:From: alexander lunyovDate: 2008-04-24 05:34:19
Subject: Re: Exceeded maximum lock level

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group