pt-online-schema-change docs don't mention default values

Bug #1016114 reported by Baron Schwartz
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Percona Toolkit moved to https://jira.percona.com/projects/PT
Fix Released
Medium
Brian Fraser

Bug Description

As shown in Peter's recent blog post, if you add a column without a default value and make it NOT NULL, pt-online-schema-change will fail during the row-copy phase. We should document this in --alter and mention that a default value is needed for NOT NULL columns.

Related branches

Brian Fraser (fraserbn)
Changed in percona-toolkit:
assignee: nobody → Brian Fraser (fraserbn)
milestone: none → 2.1.3
status: Confirmed → Fix Committed
Changed in percona-toolkit:
importance: Undecided → Medium
Changed in percona-toolkit:
status: Fix Committed → Fix Released
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-545

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.