Re: Avoiding redundant fetches of btree index metapages - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Avoiding redundant fetches of btree index metapages
Date
Msg-id 20060425175253.GC28043@surnet.cl
Whole thread Raw
In response to Avoiding redundant fetches of btree index metapages  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> Some experimentation over the weekend turned up the result that $SUBJECT 
> is a good idea.  I had never thought about this much before, figuring
> that in a heavily-used index the metapage would stay in cache anyway and
> so fetching it at the start of each index search isn't costing any extra
> I/O.  That's true, but what it does cost is bufmgr contention, and in
> fact more than you'd expect because the amount of work actually done
> before releasing the page again is minuscule.  (See off-list discussion
> attached below.)

Wow, this is extremely nice.  Congratulations on another well-spotted
performance problem solved.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Avoiding redundant fetches of btree index metapages
Next
From: Tom Lane
Date:
Subject: Re: Catalog Access (was: [GENERAL] Concurrency problem building indexes)