Postgres Pro
Downloads
Home   >   mailing lists

Re: Suboptimal plan when IN(...), ORDER BY and LIMIT are used (no JOINs) - Mailing list pgsql-general

From Michael Lewis
Subject Re: Suboptimal plan when IN(...), ORDER BY and LIMIT are used (no JOINs)
Date
Msg-id CAHOFxGo0mB+9WFBgFyZh3UzUkrpJ58cbx5t8W7D-qz6_YLc_Mw@mail.gmail.com
Whole thread Raw
In response to Suboptimal plan when IN(...), ORDER BY and LIMIT are used (no JOINs)  (Dmitry Koterov <dmitry.koterov@gmail.com>)
Responses Re: Suboptimal plan when IN(...), ORDER BY and LIMIT are used (no JOINs)  (Dmitry Koterov <dmitry.koterov@gmail.com>)
List pgsql-general
Tree view
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.

pgsql-general by date:

Previous
From: Moris Rumenov Vrachovski
Date:
Subject: Vulnerability PostgreSQL 11.2
Next
From: Dmitry Koterov
Date:
Subject: Re: Suboptimal plan when IN(...), ORDER BY and LIMIT are used (no JOINs)