explain.depesz.com

PostgreSQL's explain analyze made readable

Result: 9Tpg

Settings
# exclusive inclusive rows x rows loops node
1. 0.002 9.603 ↑ 1.0 20 1

Limit (cost=1.26..1,298.33 rows=20 width=1,269) (actual time=3.276..9.603 rows=20 loops=1)

2. 0.015 9.601 ↑ 2.5 20 1

Nested Loop (cost=1.26..3,179.08 rows=49 width=1,269) (actual time=3.275..9.601 rows=20 loops=1)

3. 0.010 7.646 ↑ 2.5 20 1

Nested Loop (cost=0.84..2,302.48 rows=50 width=865) (actual time=1.355..7.646 rows=20 loops=1)

4. 6.256 6.256 ↑ 2.5 20 1

Index Scan using posts_date_desc_idx on posts (cost=0.42..1,883.92 rows=50 width=828) (actual time=0.020..6.256 rows=20 loops=1)

  • Index Cond: ((date >= '2019-05-05 14:00:00'::timestamp without time zone) AND (date <= '2019-05-13 13:59:59.999999'::timestamp without time zone))
  • Filter: ((text_search_words @@ '''rockend'' | ''evergen'' | ''digiv'' | ''barilla'' | ''pasta'' | ''food'' | ''microsoft'' | ''race'''::tsquery) OR (mentioned_uids && '{urn:li:organiz
  • Rows Removed by Filter: 1
5. 1.380 1.380 ↑ 1.0 1 20

Index Scan using handles_id_platform_id_index on handles handle (cost=0.42..8.36 rows=1 width=37) (actual time=0.069..0.069 rows=1 loops=20)

  • Index Cond: (id = posts.handle_id)
  • Filter: (platform_id = ANY ('{1,3,4}'::integer[]))
6. 1.940 1.940 ↑ 4.0 1 20

Index Scan using handle_histories_handle_end_timestamp_unique_index on handle_histories handle_history (cost=0.42..17.49 rows=4 width=404) (actual time=0.097..0.097 rows=1 loops=20)

  • Index Cond: (handle_id = handle.id)
Planning time : 43.839 ms
Execution time : 9.694 ms