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.94.2) (envelope-from ) id 1rhBqr-00A6e5-BD for pgsql-bugs@arkaria.postgresql.org; Mon, 04 Mar 2024 17:11:45 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rhBqp-009ac6-QY for pgsql-bugs@arkaria.postgresql.org; Mon, 04 Mar 2024 17:11:44 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rhBqp-009abx-IS for pgsql-bugs@lists.postgresql.org; Mon, 04 Mar 2024 17:11:44 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rhBqj-002klK-Fb for pgsql-bugs@lists.postgresql.org; Mon, 04 Mar 2024 17:11:43 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 424HBXQc3747367; Mon, 4 Mar 2024 12:11:34 -0500 From: Tom Lane To: horst.reiterer@fabasoft.com cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #18375: requested statistics kind "f" is not yet built for statistics object 16722 In-reply-to: <18375-ba99383eb9062d6a@postgresql.org> References: <18375-ba99383eb9062d6a@postgresql.org> Comments: In-reply-to PG Bug reporting form message dated "Mon, 04 Mar 2024 07:19:33 +0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3747365.1709572293.1@sss.pgh.pa.us> Date: Mon, 04 Mar 2024 12:11:33 -0500 Message-ID: <3747366.1709572293@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk PG Bug reporting form writes: > Since upgrading from 15.5 to 15.6, the following error occurs once during a > test run: > requested statistics kind "f" is not yet built for statistics object > 16722 > mcv.c:577 statext_mcv_load > Statement: DELETE FROM test WHERE (col3 IN > (501,502,503,504,505,506,507,508,509,510,511,512,513,514,515,516,517,518,51] I could not reproduce this on the basis of the supplied information. Can you put together a self-contained test case, that is a SQL script that reproduces the failure starting from an empty database? regards, tom lane