Feedback-ID: ie0a040ee:Fastmail
Message-ID: <5ab8c4cf-9393-401e-8997-fc55d03ecc19@eisentraut.org>
Date: Mon, 27 Jan 2025 16:47:35 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: SQL:2011 application time
To: Tom Lane <tgl@sss.pgh.pa.us>, Paul Jungwirth <pj@illuminatedcomputing.com>
Cc: jian he <jian.universality@gmail.com>,
 PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>,
 vignesh C <vignesh21@gmail.com>
References: <CA+renyUApHgSZF9-nd-a0+OPGharLQLO=mDHcY4_qQ0+noCUVg@mail.gmail.com>
 <66e47fc0-77b7-4763-9b70-5c0b7ff15f21@eisentraut.org>
 <a2ee0c1a-5ef0-43ab-897c-b56adb25b34f@illuminatedcomputing.com>
 <333d3886-b737-45c3-93f4-594c96bb405d@eisentraut.org>
 <e8e51e74-10d7-410d-a1d1-8ec681d8436a@eisentraut.org>
 <f4056005-0fb7-417a-bcb3-e704f9aeadc3@illuminatedcomputing.com>
 <6a2247d9-461d-4b0a-b692-f0f3c0fab27f@eisentraut.org>
 <8f995a4c-64e3-40cd-bfed-06b54a280d36@illuminatedcomputing.com>
 <0832f18d-523f-4c15-acb0-338a785150c5@illuminatedcomputing.com>
 <5f0c25de-2c13-4fb5-a4df-a1e03c43cd14@illuminatedcomputin! g.com>
 <1b45f81d-4e99-4813-a2c6-72bf5fd80980@eisentraut.org>
 <3611540.1737518430@sss.pgh.pa.us>
 <9bb3eea7-820f-4932-92cb-cb564fc44caf@eisentraut.org>
 <bca3e7e6-ac1f-476d-9725-d6aec9100ed0@illumin! atedcomputing.com>
 <246156.1737674914@sss.pgh.pa.us> <c46c47dc!
 -cbea-4ca8-8ec9-30b7e239251f@illuminatedcomputing.com>
 <271901.1737687304@sss.pgh.pa.us>
Content-Language: en-US
From: Peter Eisentraut <peter@eisentraut.org>
In-Reply-To: <271901.1737687304@sss.pgh.pa.us>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://www.postgresql.org/message-id/5ab8c4cf-9393-401e-8997-fc55d03ecc19%40eisentraut.org>
Precedence: bulk

On 24.01.25 03:55, Tom Lane wrote:
> Paul Jungwirth <pj@illuminatedcomputing.com> writes:
>> On 1/23/25 15:28, Tom Lane wrote:
>>> I've only noticed the two, but I did not mount an aggressive search.
>>> It's possible that there were failures before 1772d554b0, since I
>>> now see that the diff is in a test case that is older than that.
> 
>> Okay, I'll keep in mind that it could be older.
> 
> I've now run an exhaustive search through the last three months of
> buildfarm runs, and found just one additional instance of the same
> failure.  The three matches are
> 
> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=calliphoridae&dt=2025-01-22%2005%3A49%3A08
> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=indri&dt=2025-01-22%2001%3A29%3A35
> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=mylodon&dt=2025-01-22%2001%3A17%3A14
> 
> Since those are all post-1772d554b0, it's difficult to avoid the
> conclusion that that either introduced the error or allowed a
> pre-existing problem to become visible.

I found a few more in the bowels of various Cirrus CI jobs:

https://cirrus-ci.com/task/5125479033733120
-> 
https://api.cirrus-ci.com/v1/artifact/task/5125479033733120/testrun/build/testrun/regress/regress/regression.diffs

https://cirrus-ci.com/task/4562529080311808
-> 
https://api.cirrus-ci.com/v1/artifact/task/4562529080311808/log/src/test/recovery/tmp_check/regression.diffs

https://cirrus-ci.com/task/5985049025183744
-> 
https://api.cirrus-ci.com/v1/artifact/task/5985049025183744/log/src/bin/pg_upgrade/tmp_check/regression.diffs

https://cirrus-ci.com/task/4702566639992832
-> 
https://api.cirrus-ci.com/v1/artifact/task/4702566639992832/log/src/test/recovery/tmp_check/regression.diffs