Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nbQrL-0005QC-Ui for pgsql-hackers@arkaria.postgresql.org; Mon, 04 Apr 2022 17:51:23 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nbQrK-00067M-F8 for pgsql-hackers@arkaria.postgresql.org; Mon, 04 Apr 2022 17:51:22 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nbQrK-00065j-5J for pgsql-hackers@lists.postgresql.org; Mon, 04 Apr 2022 17:51:22 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nbQrH-0000JL-O3 for pgsql-hackers@postgresql.org; Mon, 04 Apr 2022 17:51:21 +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 234HpDbp1923707; Mon, 4 Apr 2022 13:51:13 -0400 From: Tom Lane To: Mark Dilger cc: Thomas Munro , PostgreSQL-development , Joshua Brindle , Robert Haas , Andrew Dunstan , Jeff Davis , Joe Conway Subject: Re: New Object Access Type hooks In-reply-to: <1922986.1649094077@sss.pgh.pa.us> References: <47F87A0E-C0E5-43A6-89F6-D403F2B45175@enterprisedb.com> <17BD82D7-49AC-40C9-8204-E7ADD30321A0@enterprisedb.com> <1918971.1649091790@sss.pgh.pa.us> <1922986.1649094077@sss.pgh.pa.us> Comments: In-reply-to Tom Lane message dated "Mon, 04 Apr 2022 13:41:17 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1923705.1649094673.1@sss.pgh.pa.us> Date: Mon, 04 Apr 2022 13:51:13 -0400 Message-ID: <1923706.1649094673@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk I wrote: > Is our CI setup failing to capture stderr from TAP tests?? Oh, I'm barking up the wrong tree. This test must have been run against HEAD between 6da65a3f9 (23 Feb) and 2beb4acff (31 Mar), when pump_until indeed didn't print this essential information :-( If you just got this failure, could you look in the log to see if there's a pump_until report? regards, tom lane