Bypassing shared_buffers

Поиск
Список
Период
Сортировка
От Vladimir Churyukin
Тема Bypassing shared_buffers
Дата
Msg-id CAFSGpE3y_oMK1uHhcHxGxBxs+KrjMMdGrE+6HHOu0vttVET0UQ@mail.gmail.com
обсуждение исходный текст
Ответы Re: Bypassing shared_buffers  (Vladimir Churyukin <vladimir@churyukin.com>)
Re: Bypassing shared_buffers  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Bypassing shared_buffers  (Andrey M. Borodin <x4mmm@yandex-team.ru>)
Список pgsql-hackers
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

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Michael Paquier
Дата:
Сообщение: Re: allow granting CLUSTER, REFRESH MATERIALIZED VIEW, and REINDEX
Следующее
От: Vladimir Churyukin
Дата:
Сообщение: Re: Bypassing shared_buffers