| From: | preetika tyagi <preetikatyagi(at)gmail(dot)com> |
|---|---|
| To: | "pgsql-general(at)postgresql(dot)org General" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Shared Buffer Size |
| Date: | 2011-05-27 19:36:35 |
| Message-ID: | BANLkTikPn1k2cvMyM6t-VCSXGExuL5wYvQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi All,
I am little confused about the internal working of PostgreSQL. There is a
parameter shared_buffer in postgres.conf and I am assuming that it is used
for buffer management in PostgreSQL. If there is a need to bring in a new
page in the buffer and size exceeds the shared_buffer limit, a victim dirty
page will be written back to the disk.
However, I have read on many links that PostgreSQL depends on the OS for
caching. (http://www.varlena.com/GeneralBits/Tidbits/perf.html#shbuf)
So my question is, the actual limit of the shared buffer will be defined by
OS or the shared_buffer parameter in the postgres.conf to figure whether a
victim dirty page needs to be selected for disk write or not?
Thanks!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Johnston | 2011-05-27 20:48:42 | Re: SELECT COUNT(*) execution time on large tables (v9.0.4-1) |
| Previous Message | Samuel Gendler | 2011-05-27 19:28:22 | Re: [SQL] Re: 500KB PDF files for postgresql8.3, which is the most efficient way? |