Bug #104643 Defaults in performance schema tables incompatible with sql_mode
| Submitted: | 17 Aug 2021 14:11 | Modified: | 6 Oct 2021 16:24 |
|---|---|---|---|
| Reporter: | Sveta Smirnova (OCA) | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Performance Schema | Severity: | S3 (Non-critical) |
| Version: | 8.0.26 | OS: | Any |
| Assigned to: | Marc ALFF | CPU Architecture: | Any |
[17 Aug 2021 14:11]
Sveta Smirnova
[17 Aug 2021 18:30]
Marc ALFF
Thanks Sveta. Verified as described. Other performance schema tables are also affected: malff@localhost.localdomain:perfschema> pwd /home/malff/CODE/GIT/GIT_80/storage/perfschema malff@localhost.localdomain:perfschema> grep TIMESTAMP *.cc | grep "default 0" table_ees_by_account_by_error.cc: " FIRST_SEEN TIMESTAMP(0) null default 0,\n" table_ees_by_account_by_error.cc: " LAST_SEEN TIMESTAMP(0) null default 0,\n" table_ees_by_host_by_error.cc: " FIRST_SEEN TIMESTAMP(0) null default 0,\n" table_ees_by_host_by_error.cc: " LAST_SEEN TIMESTAMP(0) null default 0,\n" table_ees_by_thread_by_error.cc: " FIRST_SEEN TIMESTAMP(0) null default 0,\n" table_ees_by_thread_by_error.cc: " LAST_SEEN TIMESTAMP(0) null default 0,\n" table_ees_by_user_by_error.cc: " FIRST_SEEN TIMESTAMP(0) null default 0,\n" table_ees_by_user_by_error.cc: " LAST_SEEN TIMESTAMP(0) null default 0,\n" table_ees_global_by_error.cc: " FIRST_SEEN TIMESTAMP(0) null default 0,\n" table_ees_global_by_error.cc: " LAST_SEEN TIMESTAMP(0) null default 0,\n" table_esms_by_digest.cc: " FIRST_SEEN TIMESTAMP(6) NOT NULL default 0,\n" table_esms_by_digest.cc: " LAST_SEEN TIMESTAMP(6) NOT NULL default 0,\n" table_esms_by_digest.cc: " QUERY_SAMPLE_SEEN TIMESTAMP(6) NOT NULL default 0,\n" table_host_cache.cc: " FIRST_SEEN TIMESTAMP(0) NOT NULL default 0,\n" table_host_cache.cc: " LAST_SEEN TIMESTAMP(0) NOT NULL default 0,\n" table_host_cache.cc: " FIRST_ERROR_SEEN TIMESTAMP(0) null default 0,\n" table_host_cache.cc: " LAST_ERROR_SEEN TIMESTAMP(0) null default 0,\n" table_replication_applier_filters.cc: " ACTIVE_SINCE TIMESTAMP(6) NOT NULL default 0,\n" table_replication_applier_global_filters.cc: " ACTIVE_SINCE TIMESTAMP(6) NOT NULL default 0\n",
[6 Oct 2021 16:24]
Edward Gilmore
Posted by developer: Noted in 8.0.27 changelog: Several performance_schema tables contained default timestamp values of 0 (zero) which conflicted with the default sql_mode values NO_ZERO_IN_DATE and NO_ZERO_DATE. For example, attempting to create a new table based on such a performance_schema table, resulted in an error similar to the following: ERROR 1067 (42000): Invalid default value for 'FIRST_SEEN' Default timestamp values were removed from the following tables: - events_errors_summary_by_account_by_error - events_errors_summary_by_host_by_error - events_errors_summary_by_thread_by_error - events_errors_summary_by_user_by_error - events_errors_summary_global_by_error - events_statements_summary_by_digest - host_cache - replication_applier_filters - replication_applier_global_filters
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.039 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.