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 1qYL6o-001Qxm-1Z for pgsql-committers@arkaria.postgresql.org; Tue, 22 Aug 2023 06:43:22 +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 1qYL6m-00FbFV-Ng for pgsql-committers@arkaria.postgresql.org; Tue, 22 Aug 2023 06:43:20 +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 1qYL6l-00FbEt-68 for pgsql-committers@lists.postgresql.org; Tue, 22 Aug 2023 06:43:20 +0000 Received: from out4-smtp.messagingengine.com ([66.111.4.28]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qYL6f-000Jqp-HW for pgsql-committers@lists.postgresql.org; Tue, 22 Aug 2023 06:43:18 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id D670F5C25F4; Tue, 22 Aug 2023 02:43:10 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Tue, 22 Aug 2023 02:43:10 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eisentraut.org; h=cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm3; t= 1692686590; x=1692772990; bh=1wgz3hV1rOTc/Wn0u0UFLnEIOegxrR+H2Rt VapiX/tM=; b=aisK+Uj0i6C6h+6SXvNqJCKogrW+SfRY0Ve30c5lnoj7Lu0nRqq o4waL76EvOcfrd3ejOo277hiMWAXDvjELeIvPp0/8IIbieZSn3d0S1ah6RaH/s3u v5EJp5kYl/R7PjlPZSlW7dF/bnPnGz2CYQi4elwk06viPlusBtbUi7w/HlPGVIIm Uw107rO7JYSEhKteX4lOocewhRzO5dgoIahWLxCGLfSQ8+Ao8UMqQultNsJdRABW rFAV+rwmay8vlkJQx7Iqaufz2hdcNH0SWQ8YCucvBCyr13cZpBnmwHO47+QpoJAO eL3XJ3TwSej2On2ia9FhWLDHvDdAgbGMsIg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1692686590; x= 1692772990; bh=1wgz3hV1rOTc/Wn0u0UFLnEIOegxrR+H2RtVapiX/tM=; b=k MfRAXQNgml8Wmg9SM/w8f5d8JDKfoG/JGkJJmLC2sQZQDabGnF0iRKBFIXH/1ugh aXDj+2zKCxmTZ/dYi2GT4U/xpkxv6yz4PQehsLCZLcirHEsAEw/9zYiBamGJBGjU Ev9Y/r5sqPwX6dLZTH+w87r+X5S7QsfKrvfKZvIrxwaJ/ee5r07WlaN4uvHGhzoy fSZPGZrHlnhTt4/mRe0IH5UCcAbtPWQkVGOiaVxbqVEwNilG6xQcCgZ2E/Amktf+ dRcZDESkeaCxDQzOIRiIxLoXgb7df5ENGiBBnt58y9McHzrsdtv3JuaFuHoquavT ABveao9XvgV3h6X+uN6mw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedruddvtddguddufecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefkffggfgfuvfhfhfgjtgfgsehtjeertddtfeejnecuhfhrohhmpefrvght vghrucfgihhsvghnthhrrghuthcuoehpvghtvghrsegvihhsvghnthhrrghuthdrohhrgh eqnecuggftrfgrthhtvghrnhepieevfeekleehiefhledugeeliedugfegvddtledvgffg heekjedvfeetjedvhedtnecuffhomhgrihhnpehpohhsthhgrhdrvghspdhpohhsthhgrh gvshhqlhdrohhrghenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhl fhhrohhmpehpvghtvghrsegvihhsvghnthhrrghuthdrohhrgh X-ME-Proxy: Feedback-ID: ie0a040ee:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 22 Aug 2023 02:43:10 -0400 (EDT) Message-ID: Date: Tue, 22 Aug 2023 08:43:08 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.13.0 Subject: Re: pgsql: Improve BRIN minmax-multi opclass test coverage Content-Language: en-US To: Tomas Vondra , pgsql-committers@lists.postgresql.org References: From: Peter Eisentraut In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk These new tests introduced a few new calls of the md5() function. This should be avoided (see commit 208bf364a9). You can replace these easily with the fipshash() function instead, but I think you then also need to change some of the constants in the tests. Could you look at this again? On 02.07.23 10:34, Tomas Vondra wrote: > Improve BRIN minmax-multi opclass test coverage > > Per the code coverage report, the existing regression tests did not > exercice some a couple important BRIN minmax-multi code paths. > > - The tests focused on testing planning with a range of scan key > strategies, but not the execution. Fixed by adding queries that > actually test query execution for both equality and inequality. > > - All tests created indexes after inserting data, but this only > exercises the CREATE INDEX strategy that sees all values at once, not > incremental summary updates. The new tests flip the order and create > the index before adding data. > > - The assert check(s) validating correctness of expanded ranges were > present only in the "union" code path, which is not covered by > regression tests at all (as it requires concurrency etc.). Fixed by > adding the asserts to a couple more places. > > Reviewed-by: Heikki Linnakangas > Discussion: https://postgr.es/m/57020b2e-d9c9-9bc7-4892-b36d9bb07563%40enterprisedb.com > > Branch > ------ > master > > Details > ------- > https://git.postgresql.org/pg/commitdiff/0457109344b46f481f9bf09b85674695ba57c8e4 > > Modified Files > -------------- > src/backend/access/brin/brin_minmax_multi.c | 9 + > src/test/regress/expected/brin_multi.out | 357 ++++++++++++++++++++++++++++ > src/test/regress/sql/brin_multi.sql | 165 +++++++++++++ > 3 files changed, 531 insertions(+) >