explain.depesz.com

PostgreSQL's explain analyze made readable

Result: 2GJD

Settings
# exclusive inclusive rows x rows loops node
1. 1,167.766 1,362.737 ↓ 0.0 0 1

Update on public.t271_oppdim t1 (cost=1.13..992,380.02 rows=364,383 width=728) (actual time=1,362.736..1,362.737 rows=0 loops=1)

  • Buffers: shared hit=18892 read=864
2. 0.738 194.971 ↑ 327.7 1,112 1

Nested Loop (cost=1.13..992,380.02 rows=364,383 width=728) (actual time=0.327..194.971 rows=1,112 loops=1)

  • Output: t1.vid, t1.sid, t1.start_stamp, t1.end_stamp, t1.load_stamp, t1.load_id, t1.source_id, t1.field_info, t1.uncertainty_duration, t1.first, t1.deleted, t1.next_history_field_change_stamp, t1.c964_nid, t1.c965_accountid, t1.c966_accountidnid, t1.c967_name, t
  • Buffers: shared hit=2821 read=118
3. 182.835 182.835 ↑ 16.0 139 1

Index Scan using t271_oppdim_sidendstampunique on public.t271_oppdim t2 (cost=0.56..9,132.79 rows=2,219 width=97) (actual time=0.274..182.835 rows=139 loops=1)

  • Output: t2.c985_type, t2.c986_typesid, t2.c990_nextstep, t2.ctid, t2.sid
  • Index Cond: ((t2.sid = ANY ('{2323,43,123,54333,2322,32,6545,6576,12,3445,355,8768,232,543,877,473,2765,9876,6543,322,987,10,99,44,22,777,888,222,333,999,5920,3719,29209,7234,54322,87444,2383,49,113,55333,2522,62,6645,6976,1211,3345,455,8668,212,593,837,49
  • Buffers: shared hit=707 read=114
4. 11.398 11.398 ↑ 14.6 8 139

Index Scan using t271_oppdim_sidendstampunique on public.t271_oppdim t1 (cost=0.56..441.93 rows=117 width=635) (actual time=0.025..0.082 rows=8 loops=139)

  • Output: t1.vid, t1.sid, t1.start_stamp, t1.end_stamp, t1.load_stamp, t1.load_id, t1.source_id, t1.field_info, t1.uncertainty_duration, t1.first, t1.deleted, t1.next_history_field_change_stamp, t1.c964_nid, t1.c965_accountid, t1.c966_accountidnid, t1.c967_n
  • Index Cond: (t1.sid = t2.sid)
  • Buffers: shared hit=2114 read=4
Planning time : 5.720 ms
Execution time : 1,362.944 ms