Re: Bypassing shared_buffers

From: Vladimir Churyukin <vladimir(at)churyukin(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Bypassing shared_buffers
Date: 2023-06-15 01:14:06
Message-ID: CAFSGpE2L3SKH9biLNWYzjja4ZpcwdvGwosi8zp3M4xbLZ1WSBw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

To be clear, I'm talking about bypassing shared buffers for reading data /
indexes only, not about disabling it completely (which I guess is
impossible anyway).

-Vladimir Churyukin

On Wed, Jun 14, 2023 at 5:57 PM Vladimir Churyukin <vladimir(at)churyukin(dot)com>
wrote:

> Hello,
>
> 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?
>
> Thanks,
> -Vladimir Churyukin
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2023-06-15 01:22:30 Re: Bypassing shared_buffers
Previous Message Vladimir Churyukin 2023-06-15 00:57:31 Bypassing shared_buffers