public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tom Lane <[email protected]>
To: Paul Jungwirth <[email protected]>
Cc: Peter Eisentraut <[email protected]>
Cc: jian he <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Cc: vignesh C <[email protected]>
Subject: Re: SQL:2011 application time
Date: Thu, 23 Jan 2025 18:28:34 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <CA+renyUApHgSZF9-nd-a0+OPGharLQLO=mDHcY4_qQ0+noCUVg@mail.gmail.com>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<5f0c25de-2c13-4fb5-a4df-a1e03c43cd14@illuminatedcomputin! g.com>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<bca3e7e6-ac1f-476d-9725-d6aec9100ed0@illumin! atedcomputing.com>

Paul Jungwirth <[email protected]> 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

view thread (23+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: SQL:2011 application time
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox