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 1v1jQC-00C2qz-UM for pgsql-performance@arkaria.postgresql.org; Thu, 25 Sep 2025 10:41:56 +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 1v1jQB-001pDz-J2 for pgsql-performance@arkaria.postgresql.org; Thu, 25 Sep 2025 10:41:55 +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 1v1jQB-001pDq-8g for pgsql-performance@lists.postgresql.org; Thu, 25 Sep 2025 10:41:55 +0000 Received: from mail1.dalibo.net ([51.159.93.128] helo=mail.dalibo.com) by makus.postgresql.org with smtp (Exim 4.96) (envelope-from ) id 1v1jQ8-002Lif-2Z for pgsql-performance@lists.postgresql.org; Thu, 25 Sep 2025 10:41:54 +0000 Received: from [192.168.1.11] (5-49-10-71.hfc.dyn.abo.bbox.fr [5.49.10.71]) by mail.dalibo.com (Postfix) with ESMTPSA id 7D85324AB1; Thu, 25 Sep 2025 12:41:19 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dalibo.com; s=a; t=1758796879; bh=yE2zUgFRtQjbbJymKO2USjy192KGuqYpEoX4A4869qU=; h=Date:Subject:From:To:Cc:References:In-Reply-To:From; b=a5MGtUWLSJQAuYDwe/EicLcQEyhv8DQkI44m0717zvAjOjbiW1f6v8coJZlFbZVoI MvrgqNo7xMb6rpwu99/X5X0l639kfut2DOO0wPAKBX1NMRH/cOS78EPctArAGmW0Yu D5Xc6aYR0RW6O0Fm74XC7S9h5a0mIZMfyYUx++xw= Message-ID: <6754b8f8-6dad-4778-8c10-b3aed4b495e4@dalibo.com> Date: Thu, 25 Sep 2025 12:41:18 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Indexes on expressions with multiple columns and operators From: =?UTF-8?Q?Fr=C3=A9d=C3=A9ric_Yhuel?= To: Andrei Lepikhov , Tom Lane Cc: "pgsql-performance@lists.postgresql.org" , Jehan-Guillaume de Rorthais , Christophe Courtois , Laurenz Albe References: <1507576.1758120083@sss.pgh.pa.us> <62133334-b844-4d0b-b248-1a8446757e5f@dalibo.com> <1916727.1758209549@sss.pgh.pa.us> <1972974.1758213639@sss.pgh.pa.us> <76fbd9ef-1fbb-49f0-bc8b-844462b18d1d@dalibo.com> <2432873.1758387110@sss.pgh.pa.us> <6ad08c0c-2c03-4b30-b5a7-dc486aa29c52@dalibo.com> <493a013c-63d1-467a-b9ec-352f77baf37a@dalibo.com> <9756a3e9-5dea-4506-a077-72a4d9c302df@gmail.com> Content-Language: fr, en-US Autocrypt: addr=frederic.yhuel@dalibo.com; keydata= xjMEXn3bgxYJKwYBBAHaRw8BAQdA6tX5FT/n5ztMWIoBdl6k5avvu65fv6ryfVzIx/aH3V3N JEYuIFlodWVsIDxmcmVkZXJpYy55aHVlbEBkYWxpYm8uY29tPsKWBBMWCAA+FiEEi7OTyf6H ePS+C6n11XGWhN8zGNUFAmZDVJ8CGwMFCQtfi90FCwkIBwIGFQoJCAsCBBYCAwECHgECF4AA CgkQ1XGWhN8zGNV65gEA6o+UrebFjn2CIAOYwP3CiiJugiM5TMH9yJyehQua5ZoA/2ChxiVn 8OUaAw/ErxJmQi1mSN0tNZBL/KhkUPBDUDQNzjgEXn3bgxIKKwYBBAGXVQEFAQEHQCuh5cLQ AtEBXHa2Fmtp0kduBu7msM7qO/gaEcdjFUdiAwEIB8J+BBgWCAAmAhsMFiEEi7OTyf6HePS+ C6n11XGWhN8zGNUFAmZDVJ8FCQtfi90ACgkQ1XGWhN8zGNWOOAEArSqePBqfd4Kx4ulACaWO 6fM+XSDfUlBAQXx9rU6DR4MBALwozl9g91tRysim6lKxggvBfp/PvbpTZNrxYLWB2fYP In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 9/23/25 12:20, Fr=C3=A9d=C3=A9ric Yhuel wrote: > On 9/22/25 23:15, Andrei Lepikhov wrote: >> I'm not sure I fully understand your case, but SQL Server demonstrates= =20 >> an interesting approach: they have a WHERE clause attached to=20 >> statistics. So, having implemented this, you may separate the whole=20 >> range of values inside the table into 'partitions' by such a WHERE=20 >> condition. >=20 > Yes, from what I understood of the documentation [1], this is exactly=20 > what I would like! I've tested it and I can confirm that it works very well. So, on SQL Server, you can do this: CREATE STATISTICS FooStats ON foo (ackid, crit) WHERE crit =3D 'WARNING'; It would be great to have a similar feature in PostgreSQL.