Comment 9 for bug 1484677

Revision history for this message
Dave Gregg (dgregg) wrote : RE: [Bug 1484677] Re: Online-Schema-Change core dump adding new columns (After) with Comments

Thanks Frank

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Frank Cizmich
Sent: Friday, August 14, 2015 2:09 PM
To: David Gregg
Subject: [Bug 1484677] Re: Online-Schema-Change core dump adding new columns (After) with Comments

Hello Dave,

I'm glad you could sort it out.
I suggest from now on you use the attached version of pt-online-schema-change which has the nasty "segmentation fault" bug fixed.
First, you'll no longer have "segmentation fault" bug (sometimes even "out of memory") Second, you'll get a proper error message from mysql if the "--alter" clause has a problem, and probably from any other error the tool encounters.
This version will be available in the next release which is due... soon

** Attachment added: "fixed version of tool"
   https://bugs.launchpad.net/percona-toolkit/+bug/1484677/+attachment/4444899/+files/pt-online-schema-change

--
You received this bug notification because you are subscribed to the bug report.
https://bugs.launchpad.net/bugs/1484677

Title:
  Online-Schema-Change core dump adding new columns (After) with
  Comments

Status in Percona Toolkit:
  New

Bug description:
  Constantly getting a Segmentation Fault when trying to add two new float columns AFTER a column and adding 'comments'.
  I have added many new columns before - successfully. So I have no clue what's going on here?

  I have managed to narrow this down to the following...
  When I remove the "AFTER column" - this appears to work.... at least a dry-run does not core dump?

  BUT - we need to be able to get these columns in a particular order.

  My statement is as follows:
  pt-online-schema-change --recursion-method=dsn=h=10.0.10.110,D=percona,t=dsns --nocheck-replication-filters --check-interval=2 --max-lag=60 --critical-load Threads_running=30 --alter "ADD GyroStupMin float DEFAULT NULL AFTER GyroStabilityTol COMMENT 'Gyro Startup time in ms defined as the time for the Gyro outputs to reach 90% of steady state values', ADD GyroStupMax float DEFAULT NULL AFTER GyroStabilityTol COMMENT 'Gyro Startup time in ms defined as the time for the Gyro outputs to reach 90% of steady state values' " h=10.0.10.110,D=ATDB,t=AccelGyroTestSpec,u=ptool,p=pswd--dry-run

  Thanks ~ Dave

To manage notifications about this bug go to:
https://bugs.launchpad.net/percona-toolkit/+bug/1484677/+subscriptions