Details
-
Bug
-
Status: Confirmed (View Workflow)
-
Major
-
Resolution: Unresolved
-
11.1.6
-
None
-
Windows on-premise
Description
Performance Schema events_stages_current table view.
The events_stages_current table contains current stage events, with each row being a record of a thread and its most recent stage event.
`timer_start`, `timer_end`, and `timer_wait` columns
The above mentioned columns values are in picoseconds.
We tried to convert picoseconds to date timestamp. but, it's not matched with current timestamp.
For example: We mentioned current time stamp along with converted value of picoseconds. We have seen 22 characters in picoseconds value.
1731044040000000000000 - 2024-11-08 11:04:00
We have cross check the same picoseconds value from select query.
"select THREAD_ID, EVENT_ID, END_EVENT_ID, EVENT_NAME, TIMER_START, TIMER_END, TIMER_WAIT from Performance_Schema.events_stages_current"
We have seen different number of characters in Timer_start, Timer_end, Timer_wait columns. So, it's confusing. We have not able to convert correct date timestamp. Please help us to resolve this issue.
Refer attachment Query_output.png
For example we tried to convert below picoseconds value into timestamp.
Picoseconds value: 87742576136700000
Converted picoseconds to seconds: 87742.576137 (Using an online converter).
Converted seconds to the current timestamp: Friday, January 2, 1970 5:52:22.576
From the above results we couldn't able to confirm this picoseconds value have a correct number of characters. Please help us to proceed this further or do u have any conversion method/query for this please update us.
Thanks in advance.