[YSQL] Request to add Event_ID to the views yb_active_session_history and yb_event_desc.

[pdvmoto]

Jira Link: DB-14762

Description

[ASH]
Sumary: It will be useful if the view yb_wait_event_desc will display an ID (wait_ev_id) that can be referred by the records in yb_wait_event_descr.

Elaborate...

The view yb_active_session_history is useful, but in some cases we want to "keep that history" and store it into a table.

There are four text-fields: wait_event, _type, _class and _component. For storing the data, having 4 text-fields, in 1000s or millions+ of (history)records, is less efficient.

Furthermore, from saving a few days of ASH-records, we found there are probably less than 100 unique combinations of
event, _type, _class, and _component. This was confirmed by yb_wait_ev_desc: 47 records in our case. Even if multiplied by the possibilities for "component" this remains a manageable nr.

Hence the suggestion to add an (event_)ID field to both views. A simple "int" would suffice for storing the ASH data into a table, saving on storage, memory and network-traffic. Anyone interested in the text-description can join to the yb_wait_event_descr.

Note: Similar arguments can be applied to root_request_id and a number fo fields that seem related to that rr.. different issue.

Issue Type

kind/enhancement

Warning: Please confirm that this issue does not contain any sensitive information

• I confirm this issue does not contain any sensitive information.