[tarantool-patches] Re: [PATCH] sql: after table rename properly update indexes

n.pettik korablev at tarantool.org
Fri Aug 17 21:26:51 MSK 2018


>> Hi! Thanks for the fixes!
>> 
>>> diff --git a/test-run b/test-run
>>> index ed45e1d..0aa25ae 160000
>>> --- a/test-run
>>> +++ b/test-run
>>> @@ -1 +1 @@
>>> -Subproject commit ed45e1dbd36ab9109b84ef7189ef9d7e4b813fb9
>>> +Subproject commit 0aa25ae8a9d4af977b3c3478cba3ccdc4ef81d35
>> 
>> Test-run is updated accidentally.
> 
> I've discarded the hunk & force-pushed the branch. Don't think
> repost is needed here.

Hello, guys. I found this seagfault on updated branch:

tarantool> box.sql.execute('CREATE TABLE t (s1 INT PRIMARY KEY)')
---
...

tarantool> box.sql.execute('CREATE INDEX i ON t (s1)')
---
...

tarantool> box.sql.execute('ALTER TABLE t RENAME TO j3')

Ctrl+C

tarantool> n:tarantool n.pettik$ ./src/tarantool 
Tarantool 2.0.4-838-g9d879b042
type 'help' for interactive help
tarantool> box.cfg{}
2018-08-17 21:26:17.797 [23781] main/101/interactive C> Tarantool 2.0.4-838-g9d879b042
2018-08-17 21:26:17.797 [23781] main/101/interactive C> log level 5
2018-08-17 21:26:17.798 [23781] main/101/interactive I> mapping 268435456 bytes for memtx tuple arena...
2018-08-17 21:26:17.798 [23781] main/101/interactive I> mapping 134217728 bytes for vinyl tuple arena...
2018-08-17 21:26:17.807 [23781] main/101/interactive I> recovery start
2018-08-17 21:26:17.807 [23781] main/101/interactive I> recovering from `./00000000000000000000.snap'
2018-08-17 21:26:17.849 [23781] main/101/interactive I> recover from `./00000000000000000000.xlog'
2018-08-17 21:26:17.849 [23781] main/101/interactive I> done `./00000000000000000000.xlog'
2018-08-17 21:26:17.850 [23781] main/101/interactive I> recover from `./00000000000000000006.xlog'
2018-08-17 21:26:17.850 [23781] main/101/interactive I> done `./00000000000000000006.xlog'
Segmentation fault
  code: SEGV_MAPERR
  addr: 0x0
  context: 0x10881f4c8
  siginfo: 0x10881f460
Current time: 1534530377
Please file a bug at http://github.com/tarantool/tarantool/issues
Attempting backtrace... Note: since the server has already crashed, 
this may fail as well
#0  0x105e087ed in print_backtrace+d
#1  0x105cbb613 in _ZL12sig_fatal_cbiP9__siginfoPv+1f3
#2  0x7fffcae1eb3a in _sigtramp+1a
#3  0x1060690b3 in corruptSchema+93
#4  0x106068f5a in sql_init_callback+25a
#5  0x105dbe73a in space_foreach_put_cb+da
#6  0x105d86460 in space_foreach+2b0
#7  0x105dbe646 in tarantoolSqlite3LoadSchema+166
#8  0x10606927a in sqlite3InitDatabase+7a
#9  0x105dba3de in sql_load_schema+de
#10 0x105d99fe7 in _ZL10box_cfg_xcv+7a7
#11 0x105d9973d in box_cfg+d
#12 0x105cb9e81 in load_cfg+861
#13 0x105dca8c1 in _ZL13lbox_cfg_loadP9lua_State+11
#14 0x105e3653d in lj_BC_FUNCC+44
#15 0x105e64b90 in lua_pcall+210
#16 0x105dec823 in luaT_call+23
#17 0x105de3761 in lua_main+d1
#18 0x105de3548 in run_script_f+8e8
#19 0x105cbaf0a in _ZL16fiber_cxx_invokePFiP13__va_list_tagES0_+1a
#20 0x105e042db in fiber_loop+bb
#21 0x106023947 in coro_init+57
Abort trap: 6





More information about the Tarantool-patches mailing list