From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andy Colson <andy(at)squeakycode(dot)net> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: remove useless ccache searching |
Date: | 2011-09-05 19:17:46 |
Message-ID: | 12840.1315250266@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andy Colson <andy(at)squeakycode(dot)net> writes:
> This patch:
> https://commitfest.postgresql.org/action/patch_view?id=597
> caches the cache because, I guess, the cache is slow.
> Simon asked, "What is making the first cache so slow?". Pavel does not know, nor how to fix it, and nobody else responded.
Well, the cache doesn't need to be "slow" to make it worthwhile to
eliminate repeated cache lookups altogether. We do that in many places.
The questions that need to be asked here are whether the speed gain is
worthwhile, whether there is any possibility of the locally cached
information becoming obsolete, whether it's done in a clean fashion,
whether it should be done somewhere else instead of right here.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2011-09-05 19:21:38 | pgindent messing up "translator: " comments |
Previous Message | Tom Lane | 2011-09-05 19:10:55 | Re: [GENERAL] pg_upgrade problem |