explain.depesz.com

PostgreSQL's explain analyze made readable

Result: ZQkS

Settings
# exclusive inclusive rows x rows loops node
1. 0.003 0.153 ↑ 1.0 20 1

Limit (cost=1.26..1,299.96 rows=20 width=1,269) (actual time=0.022..0.153 rows=20 loops=1)

2. 0.016 0.150 ↑ 2.5 20 1

Nested Loop (cost=1.26..3,183.08 rows=49 width=1,269) (actual time=0.022..0.150 rows=20 loops=1)

3. 0.001 0.114 ↑ 2.5 20 1

Nested Loop (cost=0.84..2,306.48 rows=50 width=865) (actual time=0.016..0.114 rows=20 loops=1)

4. 0.073 0.073 ↑ 2.5 20 1

Index Scan Backward using posts_date_index on posts (cost=0.42..1,887.92 rows=50 width=828) (actual time=0.009..0.073 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. 0.040 0.040 ↑ 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.001..0.002 rows=1 loops=20)

  • Index Cond: (id = posts.handle_id)
  • Filter: (platform_id = ANY ('{1,3,4}'::integer[]))
6. 0.020 0.020 ↑ 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.001..0.001 rows=1 loops=20)

  • Index Cond: (handle_id = handle.id)
Planning time : 0.904 ms
Execution time : 0.219 ms