From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Vladimir Churyukin <vladimir(at)churyukin(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Bypassing shared_buffers |
Date: | 2023-06-15 01:22:30 |
Message-ID: | 2034773.1686792150@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Vladimir Churyukin <vladimir(at)churyukin(dot)com> writes:
> There is often a need to test particular queries executed in the worst-case
> scenario, i.e. right after a server restart or with no or minimal amount of
> data in shared buffers. In Postgres it's currently hard to achieve (other
> than to restart the server completely to run a single query, which is not
> practical). Is there a simple way to introduce a GUC variable that makes
> queries bypass shared_buffers and always read from storage? It would make
> testing like that orders of magnitude simpler. I mean, are there serious
> technical obstacles or any other objections to that idea in principle?
It's a complete non-starter. Pages on disk are not necessarily up to
date; but what is in shared buffers is.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Vladimir Churyukin | 2023-06-15 01:37:00 | Re: Bypassing shared_buffers |
Previous Message | Vladimir Churyukin | 2023-06-15 01:14:06 | Re: Bypassing shared_buffers |