Hi.
I had a fight with a query planner because it doesn’t listen.
There are two indexes:
- with expression in descending order:
"offers_offer_next_update_idx" btree (offer_next_update(update_ts,
update_freq) DESC) WHERE o_archived = false
- unique with two columns:
"offers_source_id_o
ex on source_id, offer_next_update(offers.update_ts,
> offers.update_freq) and see what happens
>
> HTH
> Gerardo
>
> - Mensaje original -
>> De: "Rafał Gutkowski"
>> Para: pgsql-performance@postgresql.org
>> Enviados: Martes, 7 de Junio 2016 10:
Altough, creating index `btree (source_id)` still changes nothing. So is `btree
(source_id) WHERE o_archived = false`.
It looks like partial indexes and full indexes cannot mix togheter even if when
they have same condition.
> On 08 Jun 2016, at 10:52, Rafał Gutkowski wrote:
>
>
