Quantcast
Channel: User Schwern - Stack Overflow
Viewing all articles
Browse latest Browse all 581

Comment by Schwern on Postgresql SELECTs went from 0.6s to 10+s after killing a (different) long running SELECT query

$
0
0
Parallel Index Only Scan using positioner_moves_p7_2025_pos_id_pos_move_index_idx is where it went wrong, but the rows returned look fine indicating to me that it's not a planner problem. I would start by checking for locks. Also, positioner_moves_p5_2025_pos_id_idx is redundant with positioner_moves_p5_2025_idx and positioner_moves_p5_2025_pos_id_pos_move_index_idx.

Viewing all articles
Browse latest Browse all 581

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>