| 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-23 23:28:34 |
| Message-ID: | 246156.1737674914@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:
> I can't find a regression.diffs in the second link. Is there one? I can't tell if it's the same
> failure as in the first link as not.
It is the same, but the diff is buried in some other file,
probably regress_log_027_stream_regress.
> I ran installcheck-parallel on my own machine continuously over night and haven't been able to
> reproduce this yet. How many cases have appeared on the build farm? More than these two? And just to
> confirm: they are only since committing 1772d554b0?
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.
> The infrequent failure made me suspect a memory error. It's hard to come up with explanations.
Same error on two different machines makes it hard to credit hardware
glitches, if that's what you mean. I could believe a bad pointer
accessing unpredictable memory, but perhaps valgrind would catch that.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Paul Jungwirth | 2025-01-23 23:54:15 | Re: SQL:2011 application time |
| Previous Message | Tom Lane | 2025-01-23 23:20:24 | Re: Self contradictory examining on rel's baserestrictinfo |