Re: Remove the limit on the number of entries allowed in catcaches,

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Qingqing Zhou <zhouqq(at)cs(dot)toronto(dot)edu>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Remove the limit on the number of entries allowed in catcaches,
Date: 2006-06-15 19:18:05
Message-ID: 156.1150399085@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> The LRU moves each time we do FileRead or FileWrite, not just on
> open/close operations.

Sure, but those still require kernel calls, so the cost of a couple of
pointer swings is negligible. There's no way that the logical
complexity of sometimes maintaining LRU and sometimes not is going
to be repaid with a useful (or even measurable) speedup.

regards, tom lane

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2006-06-15 19:19:45 Re: pgsql: Clarify dynamic pl/pgsql item and add URLs.
Previous Message Bruce Momjian 2006-06-15 19:15:00 pgsql: Use posix_fadvise() to avoid kernel caching of WAL contents on

Browse pgsql-hackers by date

  From Date Subject
Next Message Stefan Kaltenbrunner 2006-06-15 19:58:27 Re: Test request for Stats collector performance improvement
Previous Message Bruce Momjian 2006-06-15 18:02:22 pgsql: Add STRICT to PL/pgSQL SELECT INTO, so exceptions are thrown if