Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1u4WVN-003IeS-5e for pgsql-hackers@arkaria.postgresql.org; Tue, 15 Apr 2025 02:58:33 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1u4WVK-005btz-MR for pgsql-hackers@arkaria.postgresql.org; Tue, 15 Apr 2025 02:58:31 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1u4WVK-005btq-CA for pgsql-hackers@lists.postgresql.org; Tue, 15 Apr 2025 02:58:31 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1u4WVJ-0007ch-05 for pgsql-hackers@lists.postgresql.org; Tue, 15 Apr 2025 02:58:30 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 53F2wSsl1489125 for ; Mon, 14 Apr 2025 22:58:28 -0400 From: Tom Lane To: pgsql-hackers@lists.postgresql.org Subject: Recent pg_rewind test failures in buildfarm MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1489123.1744685908.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Mon, 14 Apr 2025 22:58:28 -0400 Message-ID: <1489124.1744685908@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk In the last day or so, both skink and mamba have hit this in the pg_rewind test suite [1][2]: #3 0x01f03f7c in ExceptionalCondition (conditionName=3DconditionName@entr= y=3D0x2119c4c "pending_since =3D=3D 0", fileName=3DfileName@entry=3D0x2119= 454 "pgstat.c", lineNumber=3DlineNumber@entry=3D734) at assert.c:66 #4 0x01d7994c in pgstat_report_stat (force=3Dforce@entry=3Dtrue) at pgsta= t.c:734 #5 0x01d7a248 in pgstat_shutdown_hook (code=3D, arg=3D) at pgstat.c:615 #6 0x01d1e7c0 in shmem_exit (code=3Dcode@entry=3D0) at ipc.c:243 #7 0x01d1e92c in proc_exit_prepare (code=3Dcode@entry=3D0) at ipc.c:198 #8 0x01d1e9fc in proc_exit (code=3D0) at ipc.c:111 #9 0x01cd5bd0 in ProcessRepliesIfAny () at walsender.c:2294 #10 0x01cd8084 in WalSndLoop (send_data=3Dsend_data@entry=3D0x1cd7628 ) at walsender.c:2790 #11 0x01cd8f40 in StartReplication (cmd=3D0xfd048210) at walsender.c:960 #12 exec_replication_command (cmd_string=3Dcmd_string@entry=3D0xfd53c098 "= START_REPLICATION 0/3000000 TIMELINE 2") at walsender.c:2135 #13 0x01d5bd84 in PostgresMain (dbname=3D, username=3D) at postgres.c:4767 That assert appears to be several years old, and the 008_min_recovery_point.pl test script that's triggering it hasn't changed very recently either, so I'm baffled where to start digging. It has the odor of a timing problem, so maybe we just started hitting this by chance. Still ... anybody have an idea? regards, tom lane [1] https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=3Dskink&dt=3D2= 025-04-13%2018%3A55%3A03 [2] https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=3Dmamba&dt=3D2= 025-04-15%2001%3A00%3A04