RE: Performance TODO items - Mailing list pgsql-hackers

From Mikheev, Vadim
Subject RE: Performance TODO items
Date
Msg-id 3705826352029646A3E91C53F7189E320166F9@sectorbase2.sectorbase.com
Whole thread Raw
In response to Performance TODO items  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
> New TODO entries are:
> 
>     * Order duplicate index entries by tid

In other words - add tid to index key: very old idea.

>     * Add queue of backends waiting for spinlock

We shouldn't mix two different approaches for different
kinds of short-time internal locks - in one cases we need in
light lmgr (when we're going to keep lock long enough, eg for IO)
and in another cases we'd better to proceed with POSIX' mutex-es
or semaphores instead of spinlocks. Queueing backends waiting
for spinlock sounds like nonsense - how are you going to protect
such queue? With spinlocks? -:)

Vadim


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Performance TODO items
Next
From: Bill Studenmund
Date:
Subject: Re: SIGCHLD handler in Postgres C function.