Re: Brain dump: btree collapsing

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Curtis Faith" <curtis(at)galtcapital(dot)com>
Cc: "'Hannu Krosing'" <hannu(at)tm(dot)ee>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Brain dump: btree collapsing
Date: 2003-02-14 22:33:28
Message-ID: 11687.1045262008@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Curtis Faith" <curtis(at)galtcapital(dot)com> writes:
>> "Stored in the index"? And how will you do that portably?

> Sorry for the lack of rigorous language. I meant that there would be one
> mutex per index stored in the header or internal data structures
> associated with each index somewhere. Probably in the same structure the
> root node reference for each btree is stored.

Hm. A single lock that must be grabbed for operations anywhere in the
index is a concurrency bottleneck. But maybe we could avoid that.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2003-02-14 22:41:26 Re: location of the configuration files
Previous Message Bruce Momjian 2003-02-14 22:19:55 Re: client_encoding directive is ignored in postgresql.conf