Postgres doesn’t use my indexes if there’s an OR condition between 2 indexed ILIKE conditions

We have the following indexes for our Client and Warehouse tables:

PostgreSQL query with index is taking 10x longer than without

I tried to limit the amount of rows returned by adding

Postgres not using index when filtered/indexed value does not exist

In Postgres 16.2 I’ve a table Product with extra index:

When you drop an index, what could be dependent on it to need CASCADE?

If we use

(postgres) When you drop an index, what could be dependent on it to need CASCADE?

if we use

SQL Index Scan not finding value that sequential scan finds

I’ve got a query:

Why Postgres DB sorts, even though I have an index?

This is the table schema:

Why Postgres DB sorts event though I have an index?

This is the table schema:

Postgres – difference in using higher and lower cardinality indexes, if I want same data set selected

I have a target table, and set of data that I need from this table can be retrieved using filtering on different columns, with different cardinality of values. All filter cases have indexes created, and I was thinking if there is a big (potential) performance difference in using one column as filter over another. Maybe with example it will be simple to explain: