Date: Mon, 14 Sep 2026 21:55:01 +0200
From: Christoph Berg <myon@debian.org>
To: Jeremy Schneider <schneider@ardentperf.com>
Cc: PostgreSQL in Debian <pgsql-pkg-debian@lists.postgresql.org>
Subject: Re: New versions?
Message-ID: <aqhRFej_ATvqULNT@msg.df7cb.de>
References: 
 <CA+fnDAbi8+HyBBgwoXn5kfu147OWN8sJ-WdDEbyBCGHk9mPFtA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: 
 <CA+fnDAbi8+HyBBgwoXn5kfu147OWN8sJ-WdDEbyBCGHk9mPFtA@mail.gmail.com>
Archived-At: 
 <https://www.postgresql.org/message-id/aqhRFej_ATvqULNT%40msg.df7cb.de>
Precedence: bulk

Re: Jeremy Schneider
> Curious what triggered all the version bumps? I noticed pgsentinel getting
> a Debian patch version bump but I don’t see any changes in the source repo
> at salsa. Was there a change?

Hi,

for some reason I didn't investigate further, the PG 19 package didn't
pass tests anymore before recompiling:

https://jengus.postgresql.org/job/pgsentinel-autopkgtest-beta/13/architecture=amd64,distribution=sid/console

23:20:30 ### PostgreSQL 19 installcheck ###
23:20:30 Creating new PostgreSQL cluster 19/regress ...
make -C src installcheck
make[1]: Entering directory '/tmp/autopkgtest.C6ikB1/build.HiE/src/src'
echo "# +++ regress install-check in /tmp/autopkgtest.C6ikB1/build.HiE/src +++" && /usr/lib/postgresql/19/lib/pgxs/src/makefiles/../../src/test/regress/pg_regress --inputdir=./ --bindir='/usr/lib/postgresql/19/bin'    --temp-config=./pgsentinel.conf --temp-instance=./tmp_check --dbname=contrib_regression pgsentinel-test
# +++ regress install-check in /tmp/autopkgtest.C6ikB1/build.HiE/src +++
# initializing database system by running initdb
# using temp instance on port 58928 with PID 3168
# diff -U3 /tmp/autopkgtest.C6ikB1/build.HiE/src/src/expected/pgsentinel-test.out /tmp/autopkgtest.C6ikB1/build.HiE/src/src/results/pgsentinel-test.out
# --- /tmp/autopkgtest.C6ikB1/build.HiE/src/src/expected/pgsentinel-test.out	2026-08-24 17:07:22.000000000 +0000
# +++ /tmp/autopkgtest.C6ikB1/build.HiE/src/src/results/pgsentinel-test.out	2026-09-08 21:20:25.117165806 +0000
# @@ -29,11 +29,9 @@
#         THEN count(*) > 0 ELSE true END AS has_nested_queryid
#  FROM pg_active_session_history
#  WHERE nested_queryid IS NOT NULL AND nested_queryid <> queryid;
# - has_nested_queryid
# ---------------------
# - t
# -(1 row)
# -
# +ERROR:  column "nested_queryid" does not exist
# +LINE 4: WHERE nested_queryid IS NOT NULL AND nested_queryid <> query...
# +              ^
#  SELECT pgsentinel_nested_queryid_test();
#   pgsentinel_nested_queryid_test
#  --------------------------------
# @@ -54,11 +52,9 @@
#    FROM pg_active_session_history
#    WHERE top_level_query LIKE 'SELECT pgsentinel_nested_queryid_test()%'
#  );
# - has_nested_pgssh_queryids
# ----------------------------
# - t
# -(1 row)
# -
# +ERROR:  column "nested_queryid" does not exist
# +LINE 10:   SELECT nested_queryid
# +                  ^
#  DROP FUNCTION pgsentinel_nested_queryid_test();
#  select pg_sleep(3);
#   pg_sleep
# @@ -101,7 +97,7 @@
#  from ash join pgssh using (queryid);
#   pgssh_after_ash
#  -----------------
# - t
# + f
#  (1 row)
#
#  -- Exercise pgssh's collect_pgssh_on_idle path when the query disappears from ASH while collection is idle.
# @@ -119,7 +115,7 @@
#  from ash join pgssh using (queryid);
#   pgssh_after_ash
#  -----------------
# - t
# + f
#  (1 row)
#
#  begin;
not ok 1     - pgsentinel-test                         28064 ms
1..1
# 1 of 1 tests failed.

Recompiling fixed that. It was likely some change between 19 beta1 and
beta2. Usually this would show up as missing symbols or random
crashes, so this diff is unusual, but that's what it was.

Christoph