Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1x7zM8-00000000rMz-1qKC for pgsql-committers@arkaria.postgresql.org; Sat, 19 Sep 2026 18:00:08 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1x7zM6-00000005Qj2-1Tm4 for pgsql-committers@arkaria.postgresql.org; Sat, 19 Sep 2026 18:00:06 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1x7zM5-00000005Qi9-46VD for pgsql-committers@lists.postgresql.org; Sat, 19 Sep 2026 18:00:06 +0000 Received: from mail-wm2-x10.google.com ([2a00:1450:4864:31::10]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.98.2) (envelope-from ) id 1x7zM3-00000000EE3-2yOC for pgsql-committers@lists.postgresql.org; Sat, 19 Sep 2026 18:00:05 +0000 Received: by mail-wm2-x10.google.com with SMTP id 5b1f17b1804b1-49b912e4ad9so9902465e9.2 for ; Sat, 19 Sep 2026 11:00:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1789840802; x=1790445602; darn=lists.postgresql.org; h=in-reply-to:from:content-language:references:cc:to:subject :user-agent:mime-version:date:message-id:content-type:from:to:cc :subject:date:message-id:reply-to:content-type; bh=wiH/zBIH0j0tAjoBphSyEqYsGmgbDH4tobnvOqT3zY0=; b=cACdhvfZDoWkrL8VMBbKJ5xd1n6irshoAmBVSEqrV1KC0GRWo1Sdqm3qdpJEBcqK0d hd64zAXbyDKSPsKCDjkjXLNVs30moCsIA9tzqEEq77xAfuNO5u3iuz/xCsP3V5Il8N0y IV2Fo2K3jXViZ3E9rrlOkFEodDGRcReOPtlgOFOJsOw+90dMpx1sjHhDO2rUaMmcJkCT +nBxTm3vgh88z7G2DRNw8e1188dmGerRNKha+4KHnl8gPee7PrH8rq3vZYxroCUEUeqd DoAVBL1nZ7yiZV4SPMWUGrCdEU2A8X4LTtXhs+8MuCMlGkmDjPkS27hRrFiNAiNBkHQc ZmlQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20260707; t=1789840802; x=1790445602; h=in-reply-to:from:content-language:references:cc:to:subject :user-agent:mime-version:date:message-id:content-type:x-gm-gg :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to :content-type; bh=wiH/zBIH0j0tAjoBphSyEqYsGmgbDH4tobnvOqT3zY0=; b=YcFnQHoLv4V18BzubDfRTEXt9CpWC7CQSkwqVTpp72j6BUhYPy8krnBqNyzWP2mOys yme+1UqcKprekt2FXbu3H7yTSfyw40A3TIVvJBnFvwZOz4QJqyMCnel1Wz3PLYrG3dqF Nl92Vs07V7aupGf+/gqcnA14x0V+IK3HE00aldqFwPOD9qVuZhnsAxkF2AG30hmt22nj CjckYh8TaEJytyIve/Fvgkrb99JSL/kkxU+w9n5s1D5r+vbiHa82G7AYgFxLu50Dxwrq 5Q77l5vogqzfC8MYojltiLZoTrKbTbu7yNM5lpD/0UK21RE4B4FGbyqVGEOdCDRWL88C Ff0w== X-Gm-Message-State: AFuF++kx2S84HZxfkzjN72WUr1u6lJ4PC8p0if5hRrCv/ZTvpb4B9UFm sd08VIpKRZpJXoDiA6SvIOYxKAnp+/rlxE9bigHOKH6bEoSOszBF+l1W X-Gm-Gg: AYBFou1cS0hGEzDIONukeKVs+/q+RRBwk/kxOcf8ScvkfsqnBb4KMsnG3EaQA9EkfiT RgbBJIWdQODdnWNhdYy7SXlh74+nSkY+0p+Un86NU78XyT8Zc09nPoL7PjE6L4/jPWGzZcS5O9Q riGFVDxE10/qiq+oDLbXRecLWk0Jp0jZDnheMtgZpGpT0gqcc58q5s480dzkZMkSqkjUSg8jq0K WCMiGxEs7Sco/M3KBSWJtcZdUBe/pZUzsREEJLigbn3yzClmIUqbUrWW+T/cVhAMqrbvPJAlGXd pXuoPvT2d8lIpKssTRM5t2qh2U6Xd0Uxd2ybKOvJ1kuy454P4uT+YPkhuUhpMuFrFSliie8sG+H cjhpH8PWLPupZeJr7jn50vqGstdihZDEjBdk0S48e2lWNpRGzd3+4m3+f73EBv6fY6eJpOjVLGp qZ/9IbOTTRDd4w5sWWBOD0HsWq66zWXN4ga4aVfwVs2oDEblWvwS3mg8iqVTLvgoAoqphoZmwv X-Received: by 2002:a05:600c:3584:b0:49c:fc6e:a3d9 with SMTP id 5b1f17b1804b1-49fc584fa71mr110535085e9.24.1789840801685; Sat, 19 Sep 2026 11:00:01 -0700 (PDT) Received: from [192.168.0.50] ([89.149.68.133]) by smtp.gmail.com with ESMTPSA id 5b1f17b1804b1-49fcd8bc15esm64500645e9.1.2026.09.19.11.00.00 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 19 Sep 2026 11:00:01 -0700 (PDT) Content-Type: multipart/alternative; boundary="------------KZvnoqUz2Cz67CIyLDPbiPWB" Message-ID: Date: Sat, 19 Sep 2026 21:00:00 +0300 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: pgsql: Invalidate RI fast-path metadata on operator family changes To: Amit Langote , Amit Langote Cc: pgsql-committers@lists.postgresql.org References: Content-Language: en-US From: Alexander Lakhin In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------KZvnoqUz2Cz67CIyLDPbiPWB Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Hello Amit, 19.09.2026 12:14, Amit Langote wrote: >> I noticed a few BF failures, after pushing the above changes: >> >> ... >> >> I don't see any relation between these failures and my commit. window >> runs concurrently with foreign_key, but this commit's additions to the >> latter are self-contained (a private operator family in its own >> schema), so I don't see why window's plans would be affected. >> >> Does anyone see it differently? > Forgot to add that the code change is isolated too in that it only > changes what ri_triggers.c does on a pg_amop invalidation during an RI > fast-path check, not anything the planner consults. It doesn't touch > pg_constraint or how FKs feed planning, so I don't see a route from > this commit's changes to these window plans. Any effect would be > timing at most. I would not claim that I have figured this out. I've reproduced such failures locally with: test: test_setup test: create_index test: foreign_key window x100 I think the window failures are caused by these additions: +create operator family fam using btree; +create operator class int_ops for type integer using btree family fam as +  operator 1 <(integer,integer), operator 2 <=(integer,integer), +  operator 3 =(integer,integer), operator 4 >=(integer,integer), +  operator 5 >(integer,integer), function 1 btint4cmp(integer,integer); Best regards, Alexander --------------KZvnoqUz2Cz67CIyLDPbiPWB Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit
Hello Amit,

19.09.2026 12:14, Amit Langote wrote:
I noticed a few BF failures, after pushing the above changes:

...

I don't see any relation between these failures and my commit. window
runs concurrently with foreign_key, but this commit's additions to the
latter are self-contained (a private operator family in its own
schema), so I don't see why window's plans would be affected.

Does anyone see it differently?
Forgot to add that the code change is isolated too in that it only
changes what ri_triggers.c does on a pg_amop invalidation during an RI
fast-path check, not anything the planner consults. It doesn't touch
pg_constraint or how FKs feed planning, so I don't see a route from
this commit's changes to these window plans.  Any effect would be
timing at most.  I would not claim that I have figured this out.

I've reproduced such failures locally with:
test: test_setup
test: create_index
test: foreign_key window
x100

I think the window failures are caused by these additions:
+create operator family fam using btree;
+create operator class int_ops for type integer using btree family fam as
+  operator 1 <(integer,integer), operator 2 <=(integer,integer),
+  operator 3 =(integer,integer), operator 4 >=(integer,integer),
+  operator 5 >(integer,integer), function 1 btint4cmp(integer,integer);

Best regards,
Alexander
--------------KZvnoqUz2Cz67CIyLDPbiPWB--