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 1t5Tmz-006LoV-LC for pgsql-hackers@arkaria.postgresql.org; Mon, 28 Oct 2024 17:44:26 +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 1t5Tmx-008k9h-Hm for pgsql-hackers@arkaria.postgresql.org; Mon, 28 Oct 2024 17:44:23 +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.94.2) (envelope-from ) id 1t5Tmx-008k9Z-6S for pgsql-hackers@lists.postgresql.org; Mon, 28 Oct 2024 17:44:23 +0000 Received: from dd48506.kasserver.com ([85.13.164.188]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t5Tmq-003J9K-BK for pgsql-hackers@lists.postgresql.org; Mon, 28 Oct 2024 17:44:22 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oopsware.de; s=kas202409031116; t=1730137452; bh=hl2haSMxelfBqJ8mQBSlxi5gOTKLvsI1Hv68U9qvuvs=; h=Subject:From:To:Cc:Date:In-Reply-To:References:From; b=JH/Rt0Br5MxbbD30uifAWcXj0fEBslgYRf8lKST9ZAyHi/OOagIHQWkALMKxNtIIS i34fOhZd3dzXP1sRTkXkfSQWSgpC3TjYSy9EaMl7nQiW85bka5eAPGOGaELIvp3svT 2iJknVIV47jz7n/vokqRsdBU32T8uP4KZRbiRrb3qMNwYHtVeSf2R6NVTX0mafck2k YSLOIwuQmQgSMj0jbn+ds8EtWbYs+Ra+T5rOf/UEFOsPgy2jtpH+l3d/MBzf5emxtp k2ulDFO4Xl/NC1ZnjBcN4cCoXiyG83xUgCy+MAhv7bLWsjnzSzoHYIQhIze77e5hwZ gqt/iwFAKi0bg== Received: from sethos.at.struktu.ro (sethos.at.struktu.ro [46.4.183.126]) by dd48506.kasserver.com (Postfix) with ESMTPSA id 7096E86637FA; Mon, 28 Oct 2024 18:44:12 +0100 (CET) Received: from chufu.bluecherstrasse.oopsware.lan (i5C7438ED.versanet.de [92.116.56.237]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by sethos.at.struktu.ro (Postfix) with ESMTPSA id 869A559BE637; Mon, 28 Oct 2024 18:44:11 +0100 (CET) Message-ID: <90e9c41bbe7e21c5fc8815f0bb96dd97ed7fda39.camel@oopsware.de> Subject: Re: [PATCH] Add sortsupport for range types and btree_gist From: Bernd Helmle To: "Andrey M. Borodin" Cc: jian he , PostgreSQL Hackers Date: Mon, 28 Oct 2024 18:44:10 +0100 In-Reply-To: <4BADF8DD-A4D3-43AA-AA08-037F6FFA40BC@yandex-team.ru> References: <437ccbcf-8f80-2919-411d-a3af88becf6c@cybertec.at> <77f4bacbeb9d223f90b3a0bd55ef7d65407bfddd.camel@oopsware.de> <2f2e88bf1d44d06c1baf27bbf3db880f42a5cb87.camel@oopsware.de> <31f23e46f71b744fb639967169d7df4c748110af.camel@oopsware.de> <7C9400DF-66FE-4308-BAD8-92FE3D0E55C6@yandex-team.ru> <0d9fbd59de15e2fc987a850c3d1f8a79a6ede825.camel@oopsware.de> <19c62e62c79b727d2c9a82eaeecfea5017001099.camel@oopsware.de> <4BADF8DD-A4D3-43AA-AA08-037F6FFA40BC@yandex-team.ru> Autocrypt: addr=mailings@oopsware.de; prefer-encrypt=mutual; keydata=mQGiBEIM4dYRBACEnxQZ/CfR1xbCJzGOIjvh3fZpLALMm+tt237QlZm9nlLaEwCn317sT 1khPAJwhyBHSHbNFbH+LOL6ezYrg4V2Q9KHyYJDStJtC8c+D7vHVB5Jfslynx89DnCH6jb3H0j+U0 iNYmRmT18PWTZhD5RuXT+Toyz/0hH4YnJzha4VUwCggikXRuhIQ0KIzrps7/PsvasTPjUD/1aoEHR wVyk2C2hXh6GWJYq+1l+sB2d0TOnFJf2xy3Xo03Hi+BEJJdYGqJKqzd0KfsFyJYhO2GIGScSEj1hs TqAiY8OZeRqRGHe69OQEguUSVXp/jPaqU8fel8dbDDMnXkgULq8oO4T9e4GJSFqIvrlx0sJqSMFdi ihV+xCzDS40BACBrTq9tyXmyxJWzQ1/0Hx9S4sU+yeR8ztZH9xgWi1wksfHpEgZBdAkQynlI80/bC tgxfVu+LKgxeqGfMSnT9t8agpr1IGcmSbDntbn/K+3EmCze0jq8EQrZHJWiwCqraM8mnmILSEl5zn aoVoBIF062b60zZicuNeYaVgEKSHfirQgQmVybmQgSGVsbWxlIDxiZXJuZEBvb3Bzd2FyZS5kZT6I XgQTEQIAHgUCQhyP2gIbAwYLCQgHAwIDFQIDAxYCAQIeAQIXgAAKCRBRdc2OhdlKzMm4AJ9mW1np2 RXi66WzEvcIanaJkDT+xgCfZmXG/Sziz5FchI3OjXfXDZfwnNm0J0Jlcm5kIEhlbG1sZSA8YmVybm QuaGVsbWxlQG9vcHN3YXJlLmRlPoheBBMRAgAeBQJCDOHWAhsDBgsJCAcDAgMVAgMDFgIBAh4BAhe AAAoJEFF1zY6F2UrMWZgAn3MVwDBzRS5dZu1yjx7WU3E3JSheAJ41CUYMIkX/oYfWssUVYnOuedgn 8LQlQmVybmQgSGVsbWxlIDxiaEBzY2huYWVwcGNoZW5qYWdkLmRlPoheBBMRAgAeBQJCHI+pAhsDB gsJCAcDAgMVAgMDFgIBAh4BAheAAAoJEFF1zY6F2UrMYMUAn0rk8fEEY2tHGSUD7PNbk+Fwkd7MAJ 4wMfOerrvsKTrB9xmFnZ2ZUy67w7QjQmVybmQgSGVsbWxlIDxtYWlsaW5nc0Bvb3Bzd2FyZS5kZT6 IXgQTEQIAHgUCQhyPxgIbAwYLCQgHAwIDFQIDAxYCAQIeAQIXgAAKCRBRdc2OhdlKzOhrAJ4w+A3H cjTJb54lUDpyyQu6Y5dlVQCeJCFKygOVbpn4HSp4Z+R6+s4Rul60J0Jlcm5kIEhlbG1sZSA8YmVyb mQuaGVsbWxlQGN5YmVydGVjLmF0Poh4BBMRAgA4FiEEcLVWcrwQIdBqHtvMUXXNjoXZSswFAmDe1D kCGwMFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AACgkQUXXNjoXZSszs9QCfbbpKT0/Mh4PhfS6rRbm NNQC1zS8An2x1PLHPS6649DRkiYOMWTXzAlSE Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.52.4 (3.52.4-2.fc40) MIME-Version: 1.0 X-Spamd-Bar: + List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Am Samstag, dem 26.10.2024 um 11:40 +0300 schrieb Andrey M. Borodin: > First patch: > 0. We have PG_FREE_IF_COPY(), does it suits your needs? PG_FREE_IF_COPY() requires FunctionCallInfo (the macro uses PG_GETARG_POINTER() to reference the pointer value to compare), which is not usable in the context we need it. > 1. Tests do not check what actual build method is used. You can add > INJECTION_POINT("gist-sort-build") and expect a notice there or > something like that. Hmm good idea, i give it a try.=20 > 2. "Per default" -> "By default", "indexe" -> "index", "index > quality" -> NULL (in 14 quality was bad, since 15 same "quality") >=20 > Second patch: > 0. PG_FREE_IF_COPY in range_gist_cmp? :) See above. > 1. Some test of this new functionality? Right, but i am unsure where this belongs to. Perhaps to src/test/regress/sql/rangetypes.sql ? We can extend the gist tests there.