Re: Suboptimal plan when IN(...), ORDER BY and LIMIT are used (no JOINs)

[Michael Lewis <mlewis@xxxxxxxxxxx>]

Your query and explain analyze output do not seem to match.

Filter: (cred_id = '1001344096118566254'::bigint)

I don't see anything like that in your query, nor an index that would support accomplishing that without filtering after fetching the 184k rows initially like the planner does.