| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Nailah Ogeer <ogeer(at)cs(dot)queensu(dot)ca> |
| Cc: | pgsql-docs(at)postgresql(dot)org |
| Subject: | Re: Multiple Buffer pools |
| Date: | 2003-05-12 17:26:28 |
| Message-ID: | 10150.1052760388@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
Nailah Ogeer <ogeer(at)cs(dot)queensu(dot)ca> writes:
> I am currently undergoing the project of making postgres's single buffer
> pool into multiple buffer pools hopefully to decrease the number of
> physical reads. Just wondering if anyone has done some work on this
> before.
To be honest, I think this is a complete waste of effort, as the optimal
buffering scheme for Postgres relies on OS-level caching more than
PG-internal caching. But yes, it's been discussed before. See the
archives for pgsql-performance and pgsql-hackers.
> Also, I need some information on where the number of relations in
> the system is defined.
There is no very practical way to determine that. Any one backend can
only see one database, not the entire cluster; and at the time shared
memory is sized, you don't have any database access capability at all.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Viktor Vislobokov | 2003-05-14 09:14:14 | Updated version of Russian FAQ |
| Previous Message | Nailah Ogeer | 2003-05-12 16:45:12 | Multiple Buffer pools |