[MDEV-22586] INSERTs and UPDATEs that fail because they would result in data truncation do not write to log. Created: 2020-05-15 Updated: 2020-08-24 Resolved: 2020-08-24 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Data Manipulation - Insert, Data Manipulation - Update |
| Affects Version/s: | 10.2.31, 10.3.22, 10.4.12, 10.5.2 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Juan | Assignee: | Marko Mäkelä |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | need_feedback | ||
| Environment: |
CentOS 7 |
||
| Description |
|
All insert and update operations into tables with Row Size Too Large work transparently until the total size of the data in the insert or update would result in truncation, at which point they all fail with the following error displayed on the client:
However nothing is written to the log regardless of log_warnings level. |
| Comments |
| Comment by Marko Mäkelä [ 2020-07-24 ] |
|
juan.vera, can you please submit an executable SQL test case for this feature request and suggest what exactly you would want to be logged and where? Usually the complaints are the opposite: that InnoDB is writing too much to the server error log. ralf.gebhardt@mariadb.com, could performance_schema or the upcoming sys schema be a better place for logging this kind of information? |