Find the article on our blog here:
pganalyze.com/blog/5mins-post...
In E113 of "5mins of Postgres" we discuss a commonly encountered Postgres planner quirk, which is how Postgres behaves when you have a LIMIT and an ORDER BY clause, and it picks the wrong index.
Learn more about pganalyze:
pganalyze.com
pganalyze.com/newsletter
/ pganalyze
Check out the pganalyze library for eBooks, webinars, and more:
pganalyze.com/resources
📑 What we have discussed in this episode of 5mins of Postgres:
DBA StackExchange - Poor performance on query with LIMIT when I add an ORDER BY?
dba.stackexchange.com/questio...
Why is there a Sort after an Index Only Scan? - Mailinglist discussion on pgsql-performance
www.postgresql.org/message-id...
Example of bad ORDER BY + LIMIT on dbfiddle
dbfiddle.uk/D7wiXpbv
Debugging the Postgres query planner
gocardless.com/blog/debugging...
pg_hint_plan
github.com/ossc-db/pg_hint_plan
Recent Hacker News discussion on pg_hint_plan, including discussion of the ORDER BY + LIMIT problem
news.ycombinator.com/item?id=...
One WEIRD Trick for Speeding Up ORDER BY That You Probably Shouldn't Use - Blog post by Cassidy on DEV Community
dev.to/cassidycodes/one-weird...
Негізгі бет Ғылым және технология Postgres Planner Quirks: The impact of ORDER BY + LIMIT on index usage
Пікірлер: 2