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 1uYkfn-00AeRs-2L for pgsql-hackers@arkaria.postgresql.org; Mon, 07 Jul 2025 12:10:15 +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 1uYkfk-001cf8-M0 for pgsql-hackers@arkaria.postgresql.org; Mon, 07 Jul 2025 12:10:13 +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 1uYkfk-001cez-CN for pgsql-hackers@lists.postgresql.org; Mon, 07 Jul 2025 12:10:13 +0000 Received: from relay3-d.mail.gandi.net ([2001:4b98:dc4:8::223]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1uYkfi-006E3z-2q for pgsql-hackers@lists.postgresql.org; Mon, 07 Jul 2025 12:10:12 +0000 Received: by mail.gandi.net (Postfix) with ESMTPSA id 024891FCF0; Mon, 7 Jul 2025 12:10:08 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vondra.me; s=gm1; t=1751890210; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=6GrUVR5E2Pp3Ob5kXhPxemSN2/MHU594st3cqlObF/0=; b=YhFX9TJoEPvjbiV3vH6jsxi8YQlYvWWW1svDQ605ZI/BJ16C3sGFeL35bTIeoYuY8h+OdD iCd3QnlCTdIyTq2uc4PTUbGhjvSLn6Kh68zSVooUbRYsrjsfaxiUcZ7KzHmYDoiz0KpvB+ zr4Kej1JdDuOVl4PyRBtDV4IVVbDUfSKarOHMVMm+sQ8n2pAAV0UGB+2kKC5qo6k7Zzv+5 9xI9qlXmwhYcF20UD8ibufKZ1nEqRhhda0rXSjEEsoGsrQo232R6WOmwuxq4EKyZF0xXLD yIn0gDUm41N5fmGIIWX88ER9/v3rSoUhrfbG1RrJ7h8DxI15C4enHFJslY590g== Message-ID: Date: Mon, 7 Jul 2025 14:10:07 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: amcheck support for BRIN indexes To: Arseniy Mukhin , =?UTF-8?Q?=C3=81lvaro_Herrera?= Cc: PostgreSQL Hackers References: <202507061949.6tjgborub3kd@alvherre.pgsql> Content-Language: en-US From: Tomas Vondra In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-GND-State: clean X-GND-Score: -100 X-GND-Cause: gggruggvucftvghtrhhoucdtuddrgeeffedrtdefgdefudejiecutefuodetggdotefrodftvfcurfhrohhfihhlvgemucfitefpfffkpdcuggftfghnshhusghstghrihgsvgenuceurghilhhouhhtmecufedtudenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhepkfffgggfuffvvehfhfgjtgfgsehtkeertddtvdejnecuhfhrohhmpefvohhmrghsucggohhnughrrgcuoehtohhmrghssehvohhnughrrgdrmhgvqeenucggtffrrghtthgvrhhnpeeuvddvieefffefkedugefgtdeigeelgfegudehffevieehgffghefgvdduteffveenucfkphepkeeirdegledrvdeftddrvddtieenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepihhnvghtpeekiedrgeelrddvfedtrddvtdeipdhhvghloheplgdutddrudefjedrtddrvdgnpdhmrghilhhfrhhomhepthhomhgrshesvhhonhgurhgrrdhmvgdpnhgspghrtghpthhtohepfedprhgtphhtthhopegrrhhsvghnihihrdhmuhhkhhhinhdruggvvhesghhmrghilhdrtghomhdprhgtphhtthhopegrlhhvhhgvrhhrvgeskhhurhhilhgvmhhurdguvgdprhgtphhtthhopehpghhsqhhlqdhhrggtkhgvrhhssehlihhsthhsrdhpohhsthhgrhgvshhqlhdrohhrgh X-GND-Sasl: tomas@vondra.me List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 7/7/25 13:06, Arseniy Mukhin wrote: > On Sun, Jul 6, 2025 at 10:49 PM Álvaro Herrera wrote: >> >> On 2025-Jul-06, Arseniy Mukhin wrote: >> >>> Sorry, forget to run a full test run with the new patch version. Some >>> tests were unhappy with the new unknown support function. Here the new >>> version with the fix. >> >> Hello, I think this patch is probably a good idea. I don't think it >> makes sense to introduce a bunch of code in 0003 only to rewrite it >> completely in 0005. I would ask that you re-split your WITHIN_RANGE >> (0004) to appear before the amcheck code, and then write the amcheck >> code using that new functionality. > > Hi, Álvaro! > > Thank you for looking into this. > > OK, we can easily revert to the version with consistent function if > needed, so let's get rid of it. > Alvaro, what's your opinion on the introduction of the new WITHIN_RANGE? I'd probably try to do this using the regular consistent function: (a) we don't need to add stuff to all BRIN opclasses to support this (b) it gives us additional testing of the consistent function (c) building a scan key for equality seems pretty trivial What do you think? -- Tomas Vondra