On Wed, Dec 11, 2024 at 4:35 AM David Rowley <drow...@postgresql.org> wrote:
> Enable BUFFERS with EXPLAIN ANALYZE by default
FYI, I saw a harmless Cirrus CI failure which is likely tied to this
commit, affecting pg_stat_statements -- see attached diffs file.
I spotted this same issue on
http://cfbot.cputube.org/highlights/all.html. It looks like the
pg_stat_statements test is the only regression seen on CI. Note that
this includes test runs that took place with all of the current
cleanup commits that were pushed so far, so I'm confident that this
still needs to be fixed.
--
Peter Geoghegan
diff -U3
/tmp/cirrus-ci-build/contrib/pg_stat_statements/expected/level_tracking.out
/tmp/cirrus-ci-build/build/testrun/pg_stat_statements/regress/results/level_tracking.out
--- /tmp/cirrus-ci-build/contrib/pg_stat_statements/expected/level_tracking.out
2024-12-11 18:50:58.668520000 +0000
+++
/tmp/cirrus-ci-build/build/testrun/pg_stat_statements/regress/results/level_tracking.out
2024-12-11 18:54:25.371050000 +0000
@@ -914,7 +914,9 @@
QUERY PLAN
-----------------------------------------------------
Seq Scan on stats_track_tab (actual rows=0 loops=1)
-(1 row)
+ Planning:
+ Buffers: shared hit=20
+(3 rows)
SELECT toplevel, calls, query FROM pg_stat_statements
ORDER BY query COLLATE "C";
@@ -947,7 +949,9 @@
QUERY PLAN
-----------------------------------------------------
Seq Scan on stats_track_tab (actual rows=0 loops=1)
-(1 row)
+ Planning:
+ Buffers: shared hit=20
+(3 rows)
SELECT toplevel, calls, query FROM pg_stat_statements
ORDER BY query COLLATE "C";
