Message-ID: <145e1c71-c0c6-473d-bc89-86cbd106b58b@evolu-s.it>
Date: Tue, 19 Nov 2024 09:42:43 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Functions and Indexes
To: pgsql-general@lists.postgresql.org
References: <2e36a2fe-b30f-46a5-937f-3b7d94e75cb6@evolu-s.it>
 <8dfd0bd5-87e5-4de7-9f60-8a680a32bc11@evolu-s.it>
 <20241118144307.2017e712@exelion>
Content-Language: en-US, it
From: Moreno Andreo <moreno.andreo@evolu-s.it>
In-Reply-To: <20241118144307.2017e712@exelion>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://www.postgresql.org/message-id/145e1c71-c0c6-473d-bc89-86cbd106b58b%40evolu-s.it>
Precedence: bulk


On 18/11/24 15:43, Gianni Ceccarelli wrote:
> On Mon, 18 Nov 2024 15:37:57 +0100
> Moreno Andreo <moreno.andreo@evolu-s.it> wrote:
>
>> If a column appears in the WHERE clause (and so it should be placed
>> in index), in case it is "processed" in a function (see below), is it
>> possible to insert this function to further narrow down things?
> You probably want to look at
> https://www.postgresql.org/docs/current/indexes-expressional.html
>
Hi Gianni,
     correct. That's a good starting point (now I have to add complexity 
since the index should have 4 columns, one of them is referenced with LIKE)
Thanks!
Moreno