Comment 5 for bug 1472779

I tried running a schema change on something I knew would work.....but it ALSO CORE DUMPED........not sure what has changed?????? this created the triggers + table and cleaned up ?? this is operating on 105 million records and it did this immediately upon starting the operation ???

dgregg@Slave6vm:/usr/local/bin$ pt-online-schema-change --recursion-method=dsn=h=10.0.10.110,D=percona,t=dsns --nocheck-replication-filters --check-interval=2 --max-lag=5 --critical-load Threads_running=10 --alter "add column BulkID varchar (30) NOT NULL, add key ( BulkID );" h=10.0.10.110,D=ATDB,t=AccelSummary,u=root,p=pswd --execute
Found 1 slaves:
  ChiefDB2
Will check slave lag on:
  ChiefDB2
Operation, tries, wait:
  copy_rows, 10, 0.25
  create_triggers, 10, 1
  drop_triggers, 10, 1
  swap_tables, 10, 1
  update_foreign_keys, 10, 1
Altering `ATDB`.`AccelSummary`...
Creating new table...
Created new table ATDB._AccelSummary_new OK.
Waiting forever for new table `ATDB`.`_AccelSummary_new` to replicate to ChiefDB2...
Altering new table...
Altered `ATDB`.`_AccelSummary_new` OK.
2015-07-09T11:28:40 Creating triggers...
2015-07-09T11:28:40 Created triggers OK.
2015-07-09T11:28:40 Copying approximately 105672117 rows...
2015-07-09T11:28:40 Dropping triggers...
2015-07-09T11:28:40 Dropped triggers OK.
2015-07-09T11:28:40 Dropping new table...
2015-07-09T11:28:40 Dropped new table OK.
`ATDB`.`AccelSummary` was not altered.
Segmentation fault (core dumped)