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

Re: Debugging deadlocks

From: Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>
To: Paul Tillotson <pntil(at)shentel(dot)net>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Debugging deadlocks
Date: 2005-04-02 01:57:25
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-generalpgsql-hackers
On Fri, Apr 01, 2005 at 07:41:54PM -0500, Paul Tillotson wrote:


> I suppose there must be reasons not to do this, but have you considered 
> using the "slack" space (empty space) in an ordinary table "heap" page 
> to store share-locks on the tuples in that page?  (If not enough space 
> is available then you would still need to use the spilled-to-disk btree 
> structure.)

No, I hadn't considered it.  However this seems hard to do, because the
"slack space" does not have a start point; on each page, elements
(tuples) grow from the back to the front, while element pointers grow
in the reverse direction.  So I don't see how would this be done.

I've been discussing this with Bruce who has an idea completely
different from mine (basically to extend the current tuple locking
system instead of extending the lock manager).  I'm still unsure about
the whole thing.

Alvaro Herrera (<alvherre[(at)]dcc(dot)uchile(dot)cl>)
"Ni aun el genio muy grande llegaría muy lejos
si tuviera que sacarlo todo de su propio interior" (Goethe)

In response to


pgsql-hackers by date

Next:From: Joshua D. DrakeDate: 2005-04-02 03:11:14
Subject: plPHP in core?
Previous:From: Paul TillotsonDate: 2005-04-02 00:41:54
Subject: Re: Debugging deadlocks

pgsql-general by date

Next:From: Zitan BrothDate: 2005-04-02 02:00:43
Subject: Re: SELECT INTO Array?
Previous:From: Michael FuhrDate: 2005-04-02 00:57:20
Subject: Re: SELECT INTO Array?

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