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
pgsql-hackers by date:
Соглашаюсь с условиями обработки персональных данных