explain.depesz.com

PostgreSQL's explain analyze made readable

Result: 3PpG

Settings

Optimization(s) for this plan:

# exclusive inclusive rows x rows loops node
1. 0.009 196.636 ↑ 1.0 100 1

Limit (cost=172,295.42..172,295.67 rows=100 width=16) (actual time=196.623..196.636 rows=100 loops=1)

2. 12.309 196.627 ↑ 447.6 100 1

Sort (cost=172,295.42..172,407.33 rows=44,765 width=16) (actual time=196.622..196.627 rows=100 loops=1)

  • Sort Key: (GREATEST(ticket_time_bet, ticket_time_evaluation, ticket_time_cash)) DESC
  • Sort Method: top-N heapsort Memory: 32kB
3. 165.093 184.318 ↓ 1.1 49,025 1

Bitmap Heap Scan on tab_tickets tt (cost=1,180.56..170,584.53 rows=44,765 width=16) (actual time=36.319..184.318 rows=49,025 loops=1)

  • Recheck Cond: (id_client = 1035287)
  • Filter: ((id_ticket_state = ANY ('{5,6}'::integer[])) AND (id_ticket_phase = 1))
  • Heap Blocks: exact=46729
4. 19.225 19.225 ↓ 1.0 49,130 1

Bitmap Index Scan on ix_tabtickets_idclient_betdate (cost=0.00..1,169.37 rows=47,040 width=0) (actual time=19.225..19.225 rows=49,130 loops=1)

  • Index Cond: (id_client = 1035287)
Planning time : 0.559 ms
Execution time : 196.690 ms