| From: | Bill Moran <wmoran(at)potentialtech(dot)com> |
|---|---|
| To: | "Sorin N(dot) Ciolofan" <ciolofan(at)ics(dot)forth(dot)gr> |
| Cc: | <pgsql-general(at)postgresql(dot)org>, <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: [GENERAL] pg_buffercache view |
| Date: | 2007-04-26 12:32:11 |
| Message-ID: | 20070426083211.06c1c990.wmoran@potentialtech.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-general |
In response to "Sorin N. Ciolofan" <ciolofan(at)ics(dot)forth(dot)gr>:
>
> Hello!
>
> Do you know which could be the reasons that could conduce an application to
> not release the shared buffers, even after the application was shut down?
> I noticed that only if a pg_ctl restart command is issued some of the
> buffers are set free.
The reason would be "by design."
If the server flushes its cache every time the application restarts, the
cache isn't going to be very effective.
If PostgreSQL is using more shared buffers than you're comfortable with,
reduce the shared_buffers setting in the config. That will allow the OS
to decide how to use the memory instead.
--
Bill Moran
http://www.potentialtech.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Treat | 2007-04-26 12:36:11 | Re: Finding time in WAL logs |
| Previous Message | Sorin N. Ciolofan | 2007-04-26 10:01:07 | Re: [GENERAL] pg_buffercache view |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Cefull Lo | 2007-04-26 13:04:54 | Number of Queries |
| Previous Message | John DeSoi | 2007-04-26 12:03:24 | tsearch2 punctuation question |