Re: [PERFORM] Combination of partial and full indexes

gt;> actual data in the table. >> >> I will try an index on source_id, offer_next_update(offers.update_ts, >> offers.update_freq) and see what happens >> >> HTH >> Gerardo >> >> - Mensaje original - >>> De: "Rafał Gutkowski" >

Re: [PERFORM] Combination of partial and full indexes

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:

Re: [PERFORM] Combination of partial and full indexes

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:39:14 > Asunto: [PERFORM] Combination of par

[PERFORM] Combination of partial and full indexes

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