On Sat, Jun 18, 2011 at 9:21 AM, Pavel Stehule <pavel.stehule@gmail.com> wrote:
> Is this profile expected?
I've certainly seen profiles before where the catcache overhead was
significant. I don't think that I've seen SearchCatCache() quite this
high on any of the profiling I've done, but then again I don't tend to
profile the same things you do, so maybe that's not surprising. I
think the interesting question is probably "where are all those calls
coming from?" and "can we optimize any of them away?" rather than "how
do we make SearchCatCache() run faster?". I would be willing to bet
money that the latter is largely an exercise in futility.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
