Re: Bypassing shared_buffers - Mailing list pgsql-hackers

From Greg Sabino Mullane
Subject Re: Bypassing shared_buffers
Date
Msg-id CAKAnmmK1sKJs=WqGKby3dRkvnS_3hgZk6_G_fJjtWSFaCYp05g@mail.gmail.com
Whole thread Raw
In response to Re: Bypassing shared_buffers  (Vladimir Churyukin <vladimir@churyukin.com>)
List pgsql-hackers
On Thu, Jun 15, 2023 at 4:16 AM Vladimir Churyukin <vladimir@churyukin.com> wrote: 
We're trying to see what is the worst performance in terms of I/O, i.e. when the database just started up or the data/indexes being queried are not cached at all.

You could create new tables that are copies of the existing ones (CREATE TABLE foo as SELECT * FROM ...), create new indexes, and run a query on those. Use schemas and search_path to keep the queries the same. No restart needed! (just potentially lots of I/O, time, and disk space :) Don't forget to do explain (analyze, buffers) to double check things.


pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: [PATCH] ltree hash functions
Next
From: James Cloos
Date:
Subject: deb’s pg_upgradecluster(1) vs streaming replication