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

Re: Concurrent free-lock

From: Neil Conway <neilc(at)samurai(dot)com>
To: "Jonah H(dot) Harris" <jharris(at)tvi(dot)edu>
Cc: Pailloncy Jean-Gerard <jg(at)rilk(dot)com>,pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Concurrent free-lock
Date: 2005-01-24 23:23:57
Message-ID: 1106609037.1780.18.camel@localhost.localdomain (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Mon, 2005-01-24 at 08:35 -0700, Jonah H. Harris wrote:
> Lock free data structures are cool... but not really applicable to 
> databases.  They have a high maintenance overhead, severe complexity, 
> and will fail when there are many concurrent inserts/deletes to the 
> structure.

Can you elaborate on when they would fail, and why?

It might be worth considering lock-free data structures for certain
parts of the backend, but I'm skeptical they would be much of a win over
locking most of the time.


In response to


pgsql-hackers by date

Next:From: Jonah H. HarrisDate: 2005-01-24 23:50:10
Subject: Re: Concurrent free-lock
Previous:From: Bruce MomjianDate: 2005-01-24 22:12:06
Subject: In NYC Monday to Wednesday

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