| From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
|---|---|
| To: | Markus Innerebner <markus(dot)innerebner(at)inf(dot)unibz(dot)it> |
| Cc: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Question about caching on full table scans |
| Date: | 2012-08-30 18:00:32 |
| Message-ID: | CAMkU=1xZ822+Z06ZTFA8T+K8m1k4jh4tXvZuuv_cn=o+C_eTfA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Thu, Aug 30, 2012 at 10:34 AM, Markus Innerebner
<markus(dot)innerebner(at)inf(dot)unibz(dot)it> wrote:
>
> > To flush the filesystem cache (from Linux 2.6.16 on), use
> > sync; echo 3 > /proc/sys/vm/drop_caches
>
>
> I started to do that , and
> yes, this solves my problem!!
>
> I assume that deleting file system cache implies that also postgres cache is
> deleted, isn't it ?
No, the postgres-managed cache is not cleared by doing that. In order
to get rid of both layers of caching, you should restart the postgres
server and then do the drop_caches.
Cheers,
Jeff
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2012-08-30 18:13:45 | Re: Question about caching on full table scans |
| Previous Message | Markus Innerebner | 2012-08-30 17:34:56 | Re: Question about caching on full table scans |