[MDEV-27897] Serever crash virtual cloum with curdate() Created: 2022-02-19  Updated: 2022-02-21  Resolved: 2022-02-21

Status: Closed
Project: MariaDB Server
Component/s: Virtual Columns
Affects Version/s: 10.3.33, 10.5.15
Fix Version/s: N/A

Type: Bug Priority: Critical
Reporter: bulepage Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Environment:

ubuntu bionic


Issue Links:
Duplicate
duplicates MDEV-24176 Server crashes after insert in the ta... Closed
duplicates MDEV-26407 Server crashes in Item_func_in::clean... Closed

 Description   

After run this script server restart:

drop table if exists test;
CREATE TABLE test (
  bstatus tinyint,
  valid_to date,
  valid tinyint GENERATED ALWAYS AS (valid_to > curdate() and bstatus not in (1,2)) VIRTUAL
) ENGINE=InnoDB;
 
-- the table is empty
-- this select need result and valid=1
SELECT 1 FROM test WHERE valid=1;
-- without first query server dosn't crash
-- when select * form server restart  valid=1 parameter need
SELECT * FROM test where valid=1;
 
 

In logs:

 
 
 
[ERROR] mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
 
To report this bug, see https://mariadb.com/kb/en/reporting-bugs
 
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed, 
something is definitely wrong and this may fail.
 
Server version: 10.3.32-MariaDB-1:10.3.32+maria~bionic
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=1
max_threads=153
thread_count=6
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467428 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
 
Thread pointer: 0x5613433f0b58
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0x7f31d4050dd8 thread_stack 0x49000
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x56134106d98e]
/usr/sbin/mysqld(handle_fatal_signal+0x515)[0x561340b011a5]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x12980)[0x7f31d681a980]
/usr/sbin/mysqld(_ZN12Item_func_in7cleanupEv+0x37)[0x561340c13217]
/usr/sbin/mysqld(_ZN4Item17cleanup_processorEPv+0x1a)[0x561340b137fa]
/usr/sbin/mysqld(_ZN9Item_cond4walkEM4ItemFbPvEbS1_+0x45)[0x561340b33475]
/usr/sbin/mysqld(_Z21fix_session_vcol_exprP3THDP19Virtual_column_info+0x36)[0x5613409c68c6]
/usr/sbin/mysqld(_Z30fix_session_vcol_expr_for_readP3THDP5FieldP19Virtual_column_info+0x47)[0x5613409c6927]
/usr/sbin/mysqld(_ZN10Item_field10fix_fieldsEP3THDPP4Item+0xdc)[0x561340b24f3c]
/usr/sbin/mysqld(_ZN9Item_func10fix_fieldsEP3THDPP4Item+0x147)[0x561340b5e3b7]
/usr/sbin/mysqld(_Z11setup_condsP3THDP10TABLE_LISTR4ListIS1_EPP4Item+0x1ef)[0x5613408c4fdf]
/usr/sbin/mysqld(_ZN4JOIN7prepareEP10TABLE_LISTjP4ItemjP8st_orderbS5_S3_S5_P13st_select_lexP18st_select_lex_unit+0x3dc)[0x56134096357c]
/usr/sbin/mysqld(_Z12mysql_selectP3THDP10TABLE_LISTjR4ListI4ItemEPS4_jP8st_orderS9_S7_S9_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x7eb)[0x5613409735cb]
/usr/sbin/mysqld(_Z13handle_selectP3THDP3LEXP13select_resultm+0x14d)[0x56134097386d]
/usr/sbin/mysqld(+0x595941)[0x561340912941]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x5261)[0x56134091f461]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_statebb+0x1ea)[0x561340921daa]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcjbb+0xc2d)[0x56134092371d]
/usr/sbin/mysqld(_Z10do_commandP3THD+0x126)[0x561340925436]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP7CONNECT+0x336)[0x5613409fa956]
/usr/sbin/mysqld(handle_one_connection+0x3d)[0x5613409faa2d]
nptl/pthread_create.c:463(start_thread)[0x7f31d680f6db]
x86_64/clone.S:97(clone)[0x7f31d653871f]
 
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x5613433fe600): SELECT * FROM test where valid=1
 
Connection ID (thread ID): 11
Status: NOT_KILLED
 
Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on
 
The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains
information that should help you find out what is causing the crash.
Writing a core file...
Working directory at /var/lib/mysql
Resource Limits:
Limit                     Soft Limit           Hard Limit           Units     
Max cpu time              unlimited            unlimited            seconds   
Max file size             unlimited            unlimited            bytes     
Max data size             unlimited            unlimited            bytes     
Max stack size            8388608              unlimited            bytes     
Max core file size        0                    unlimited            bytes     
Max resident set          unlimited            unlimited            bytes     
Max processes             9859                 9859                 processes 
Max open files            32768                32768                files     
Max locked memory         67108864             67108864             bytes     
Max address space         unlimited            unlimited            bytes     
Max file locks            unlimited            unlimited            locks     
Max pending signals       9859                 9859                 signals   
Max msgqueue size         819200               819200               bytes     
Max nice priority         0                    0                    
Max realtime priority     0                    0                    
Max realtime timeout      unlimited            unlimited            us         



 Comments   
Comment by Alice Sherepa [ 2022-02-21 ]

Thank you for the report!
It is the same problem as MDEV-24176

Generated at Thu Feb 08 09:56:26 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.