A page may be double buffered in PG's buffer pool and in OS's buffer cache.
Other DBMS like DB2 and Oracle has provided Direct I/O option to eliminate
double buffering. I noticed there were discusses on the list. But
I can not find similar option in PG. Does PG support direct I/O now?
The tuning guide of PG usually recommends a small shared buffer pool
to the size of physical memory). I think it is to avoid swapping. If
swapping, OS kernel may swap out some pages in PG's buffer pool even PG
want to keep them in memory. i.e. PG would loose full control over
A large buffer pool is not good because it may
1. cause more pages double buffered, and thus decrease the efficiency of
cache and buffer pool.
2. may cause swapping.
Am I right?
If PG's buffer pool is small compared with physical memory, can I say
hit ratio of PG's buffer pool is not so meaningful because most misses
satisfied by OS Kernel's buffer cache?
pgsql-performance by date
|Next:||From: Michael Dengler||Date: 2007-04-05 18:01:54|
|Subject: What do the adminpack functions do? (8.2.3)|
|Previous:||From: Arjen van der Meijden||Date: 2007-04-05 16:29:42|
|Subject: Re: SCSI vs SATA|