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

Re: Debugging deadlocks

From: Paul Tillotson <pntil(at)shentel(dot)net>
To:
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Debugging deadlocks
Date: 2005-04-02 15:32:13
Message-ID: 424EBAFD.6020001@shentel.net (view raw or flat)
Thread:
Lists: pgsql-generalpgsql-hackers
Greg Stark wrote:

>Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>  
>
>>Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> writes:
>>    
>>
>>>On Fri, Apr 01, 2005 at 10:14:07PM -0500, Paul Tillotson wrote:
>>>      
>>>
>>>>...
>>>>        
>>>>
>>>Well, at that point you need to take a lock in order to be able to
>>>manage locks.  Managing not to step on your own feet in that scenario
>>>is complex, to say the least, if not downright impossible.
>>>      
>>>
>>I looked at Paul's first message and thought "nah, that won't work
>>because ... because ... hmm ... hmmm ..."
>>    
>>
>
>For what it's worth, this would be very similar to how Oracle handles such
>locks. In that case there's a fixed amount of space per page reserved in
>advance for storing locks.
>
>Actually I think it's a bit more complicated. But that's the idea.
>  
>
While we're at it, does anyone know how DB2 and MSSQL server handle 
row-level locks?

Paul

In response to

pgsql-hackers by date

Next:From: Joshua D. DrakeDate: 2005-04-02 15:33:31
Subject: Re: [HACKERS] plPHP in core?
Previous:From: Joshua D. DrakeDate: 2005-04-02 15:30:08
Subject: Re: [HACKERS] plPHP in core?

pgsql-general by date

Next:From: Joshua D. DrakeDate: 2005-04-02 15:33:31
Subject: Re: [HACKERS] plPHP in core?
Previous:From: Joshua D. DrakeDate: 2005-04-02 15:30:08
Subject: Re: [HACKERS] plPHP in core?

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