| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Paul Jungwirth <pj(at)illuminatedcomputing(dot)com> |
| Cc: | Peter Eisentraut <peter(at)eisentraut(dot)org>, jian he <jian(dot)universality(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, vignesh C <vignesh21(at)gmail(dot)com> |
| Subject: | Re: SQL:2011 application time |
| Date: | 2025-01-24 02:55:04 |
| Message-ID: | 271901.1737687304@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Paul Jungwirth <pj(at)illuminatedcomputing(dot)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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2025-01-24 03:09:07 | Re: Pgoutput not capturing the generated columns |
| Previous Message | Peter Smith | 2025-01-24 02:43:47 | Re: Enhance 'pg_createsubscriber' to retrieve databases automatically when no database is provided. |