From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
Cc: | Vladimir Churyukin <vladimir(at)churyukin(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Bypassing shared_buffers |
Date: | 2023-06-15 02:43:39 |
Message-ID: | 2043512.1686797019@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Thomas Munro <thomas(dot)munro(at)gmail(dot)com> writes:
> There are two levels of cache. If you're on Linux you can ask it to
> drop its caches by writing certain values to /proc/sys/vm/drop_caches.
> For PostgreSQL's own buffer pool, it would be nice if someone would
> extend the pg_prewarm extension to have a similar 'unwarm' operation,
> for testing like that. But one thing you can do is just restart the
> database cluster, or use pg_prewarm to fill its buffer pool up with
> other stuff (and thus kick out the stuff you didn't want in there).
But that'd also have to push out any dirty buffers. I'm skeptical
that it'd be noticeably cheaper than stopping and restarting the
server.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2023-06-15 02:49:22 | Re: [DOC] Update ALTER SUBSCRIPTION documentation v3 |
Previous Message | Peter Smith | 2023-06-15 02:42:33 | Consistent coding for the naming of LR workers |