)SELECT*FROM relaxed_resultsORDER BY distance;

For queries that filter by distance, use a materialized CTE and place the filter outside of it for best performance (due to the[current behavior](https://www.postgresql.org/message-id/flat/CAOdR5yGUoMQ6j7M5hNUXrySzaqZVGf_Ne%2B8fwZMRKTFxU1nbJg%40mail.gmail.com) of the Postgres executor)

For queries that filter by distance, use a materialized CTE and place thedistancefilter outside of it for best performance (due to the[current behavior](https://www.postgresql.org/message-id/flat/CAOdR5yGUoMQ6j7M5hNUXrySzaqZVGf_Ne%2B8fwZMRKTFxU1nbJg%40mail.gmail.com) of the Postgres executor)

WITHfiltered_resultsAS MATERIALIZED (

SELECT id, embedding<->'[1,2,3]'AS distanceFROM itemsWHERE category_id=123ORDER BY distanceLIMIT5

)SELECT*FROMfiltered_resultsWHERE distance<0.1ORDER BY distance;

WITHnearest_resultsAS MATERIALIZED (

SELECT id, embedding<->'[1,2,3]'AS distanceFROM itemsORDER BY distanceLIMIT5

)SELECT*FROMnearest_resultsWHERE distance<5ORDER BY distance;

Note: Place any other filters inside the CTE

Since scanning a large portion of an approximate index is expensive, there are options to control when a scan ends