public inbox for [email protected]  

help / color / mirror / Atom feed

From: Peter Eisentraut <[email protected]>
To: Paul Jungwirth <[email protected]>
Cc: Tom Lane <[email protected]>
Cc: jian he <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Cc: vignesh C <[email protected]>
Subject: Re: SQL:2011 application time
Date: Wed, 12 Feb 2025 16:23:36 +0100
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]>
	<5f0c25de-2c13-4fb5-a4df-a1e03c43cd14@illuminatedcomputin! g.com>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

On 05.02.25 19:31, Paul Jungwirth wrote:
> On 2/5/25 05:37, Peter Eisentraut wrote:
>> On 29.01.25 07:34, Paul Jungwirth wrote:
>>> Is it possible to commit an RI_PLAN_NO_ACTION addition and see if 
>>> that makes the buildfarm failures go away? Here is a proposed patch 
>>> for that (v48.1). I would understand if this is too questionable a 
>>> practice---but it would be nice to get sufficient test exposure to 
>>> see if it makes a difference. Since I still haven't reproduced this 
>>> locally (despite running continuously for almost a week), it's not an 
>>> experiment I can do myself. If it *does* make the failures go away, 
>>> then it suggests there is still some latent problem somewhere.
>>
>> I'm tempted to give this a try.  But the cfbot is currently in a bit 
>> of a mess, so I'll wait until that is clean again so that we can have 
>> a usable baseline to work against.
> 
> Okay, thanks! I've been spending some more time on this, but I haven't 
> made much progress.

I committed your patch on Sunday, and now it's about 72 hours later.

I've been observing this on cfbot for some time.  Before the patch, you 
could go to cfbot at any time and find between 5 and 10 test failures 
from this problem.  And now there are none.  So I'm calling provisional 
success on this.

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