pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: David Rowley <drowley@postgresql.org>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Fix further fallout from EXPLAIN ANALYZE BUFFERS change
Date: Wed, 11 Dec 2024 20:50:33 +0000
Message-ID: <E1tLTfF-002FXL-3y@gemulon.postgresql.org> (raw)

Fix further fallout from EXPLAIN ANALYZE BUFFERS change

c2a4078eb adjusted EXPLAIN ANALYZE to default the BUFFERS to ON.  This
(hopefully) fixes the last remaining issue with regression test failures
with -D RELCACHE_FORCE_RELEASE -D CATCACHE_FORCE_RELEASE builds, where
the planner accesses more buffers due to the cold caches.

Discussion: https://postgr.es/m/CAApHDvqLdzgz77JsE-yTki3w9UiKQ-uTMLRctazcu+99-ips3g@mail.gmail.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/89988ac5891b3d41725472a65e50ae4e192313aa

Modified Files
--------------
.../pg_stat_statements/expected/level_tracking.out | 24 +++++++++++-----------
contrib/pg_stat_statements/sql/level_tracking.sql  |  8 ++++----
2 files changed, 16 insertions(+), 16 deletions(-)



Message-ID: <E1tLTfF-002FXL-3y@gemulon.postgresql.org>
Permalink:  ../E1tLTfF-002FXL-3y@gemulon.postgresql.org/
Also on:    postgresql.org/message-id/E1tLTfF-002FXL-3y@gemulon.postgresql.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-committers@postgresql.org
  Cc: drowley@postgresql.org, pgsql-committers@lists.postgresql.org
  Subject: Re: pgsql: Fix further fallout from EXPLAIN ANALYZE BUFFERS change
  In-Reply-To: <E1tLTfF-002FXL-3y@gemulon.postgresql.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox