[MDEV-6258] MariaDB 10.0 performance schema timestamps relative to epoch Created: 2014-05-21  Updated: 2014-06-06  Resolved: 2014-06-06

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: 10.0.11
Fix Version/s: 10.0.12

Type: Bug Priority: Critical
Reporter: Kolbe Kegel (Inactive) Assignee: Sergei Golubchik
Resolution: Fixed Votes: 0
Labels: performance_schema
Environment:

CentOS 6


 Description   

MariaDB 10.0 and MariaDB 10.1 both show this behavior:

select first_seen, last_seen from performance_schema.events_statements_summary_by_digest;
 
+---------------------+---------------------+
 
| first_seen          | last_seen           |
 
+---------------------+---------------------+
 
| 1970-01-02 22:47:44 | 1970-01-02 22:47:44 |
 
| 1970-01-02 22:47:44 | 1970-01-02 22:47:44 |
 
| 1970-01-02 22:47:44 | 1970-01-02 22:47:44 |
 
| 1970-01-02 22:47:44 | 1970-01-02 22:47:44 |
 
| 1970-01-02 22:47:47 | 1970-01-02 22:47:47 |
 
| 1970-01-02 22:47:47 | 1970-01-02 22:47:47 |
 
| 1970-01-02 22:47:47 | 1970-01-02 22:47:48 |
 
| 1970-01-02 22:47:56 | 1970-01-02 23:06:29 |
 
| 1970-01-02 23:06:49 | 1970-01-02 23:06:49 |
 
+---------------------+---------------------+
 
9 rows in set (0.00 sec)

This is not a problem in MariaDB 10.0.11 that I built on OS X.

This also does not exist in MySQL 5.6.17.
Generated at Thu Feb 08 07:10:32 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.