From: | "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com> |
---|---|
To: | "Denis Gasparin" <denis(at)edistar(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Free Cache Memory (Linux) and Postgresql |
Date: | 2008-09-30 11:46:56 |
Message-ID: | 36e682920809300446q4108b355xbecf384b0c9d1ae2@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Sep 30, 2008 at 3:33 AM, Denis Gasparin <denis(at)edistar(dot)com> wrote:
> Hi.
>
> I'm evaluating to issue the drop_caches kernel command (echo 3 >
> /proc/sys/vm/drop_caches) in order to free unused pagecache, directory
> entries and inodes.
>
> I'm thinking to schedule the command during low load moments after
> forcing a sync command.
>
> I wonder if this can cause pgsql problems of any kind. Any idea?
Yes, it can. Postgres relies heavily on the OS' file system cache, if
you wipe it out, you're going to have quite an I/O storm on a large
database.
What are you trying to accomplish? By itself, sync will flush all
dirty file system blocks to disk and leave them in memory.
--
Jonah H. Harris, Senior DBA
myYearbook.com
From | Date | Subject | |
---|---|---|---|
Next Message | Sam Mason | 2008-09-30 12:04:29 | Re: PostgreSQL Cache |
Previous Message | Russell Smith | 2008-09-30 10:20:39 | Re: ODBC driver crash |