| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Process local hint bit cache |
| Date: | 2011-03-30 14:36:24 |
| Message-ID: | 4D933FE8.9060401@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 30.03.2011 17:05, Merlin Moncure wrote:
> *) Maybe the shared buffer cache currently being maintained over the
> clog can be scrapped. I'm going to leave it alone for now, but I'm
> quite skeptical it provides much benefit even without local process
> cache. clog page have a very nice property that you don't have to
> worry about what else is going on from other processes and thus no
> complicated locking or invalidation issues when considering cache
> structure. IMNSHO -- this makes a local cache a much better fit even
> if you have to keep it smaller for memory usage reasons.
A related idea I've sometimes pondered is to mmap() the clog in every
process.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2011-03-30 14:40:11 | Re: Process local hint bit cache |
| Previous Message | Robert Haas | 2011-03-30 14:14:03 | Re: pg_dump --binary-upgrade vs. ALTER TYPE ... DROP ATTRIBUTE |