Skip to content

Instantly share code, notes, and snippets.

@eliank

eliank/postgres-the-unwanted-side-effects-of-limit-on-query-planning-5.sql

Created May 23, 2016 11:56
Show Gist options
  • Save eliank/a0060b51ae838079345f019cf005b37e to your computer and use it in GitHub Desktop.
Save eliank/a0060b51ae838079345f019cf005b37e to your computer and use it in GitHub Desktop.
Download ZIP
Raw
postgres-the-unwanted-side-effects-of-limit-on-query-planning-5.sql
moneybird_app=> EXPLAIN ANALYZE SELECT “some_table”.”id” FROM “some_table” WHERE (some_variable IN (‘some_value’, ‘another_value’, ‘yet_another_value’) AND ((some_date <= ‘2016–05–01’ AND DATE_TRUNC(‘day’, updated_at) <= some_date) AND (“some_table”.”id” > 123456789) ORDER BY “some_table”.”id” ASC;
 — REMOVED DETAILS
Bitmap Index Scan on some_table_index (cost=0.00..1362.84 rows=53272 width=0) (actual time=30.145..30.145 rows=19102 loops=1)
 — REMOVED DETAILS
Planning time: 0.527 ms
Execution time: 4533.796 ms
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment