Improving readability of QUERY_PLAN_PROFILES output
Output from the QUERY_PLAN_PROFILES table can be very wide because of the path_line column.
Output from the
QUERY_PLAN_PROFILES table can be very wide because of the path_line column. To facilitate readability, query QUERY_PLAN_PROFILES using one or more of the following options:
-
Sort output by
transaction_id,statement_id,path_id, andpath_line_index:=> SELECT ... FROM query_plan_profiles WHERE ... ORDER BY transaction_id, statement_id, path_id, path_line_index; -
Use column aliases to decrease column width:
=> SELECT statement_id AS sid, path_id AS id, path_line_index AS order, is_started AS start, is_completed AS end, is_executing AS exe, running_time AS run, memory_allocated_bytes AS mem, read_from_disk_bytes AS read, received_bytes AS rec, sent_bytes AS sent, FROM query_plan_profiles WHERE transaction_id=45035996273910558 AND statement_id=3 ORDER BY transaction_id, statement_id, path_id, path_line_index; -
Use the vsql
\ocommand to redirectEXPLAINoutput to a file:=> \o /home/dbadmin/long-queries => EXPLAIN SELECT * FROM customer_dimension; => \o