The xtrabackup binary should recognize the --core-file option
Bug #1373429 reported by
Alexey Kopytov
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Fix Released
|
Medium
|
Alexey Kopytov | ||
| 2.1 |
Invalid
|
Undecided
|
Unassigned | ||
| 2.2 |
Fix Released
|
Medium
|
Alexey Kopytov | ||
Bug Description
Before the fix for bug #766305, the xtrabackup would create a core file on a fatal signal such as SIGSEGV, provided that the OS is properly configured. However, with the fix of that bug in PXB 2.2.5+ a core file would not be created on a fatal signal, because the standard MySQL signal handler is used. In particular, the MySQL signal handler would not create a core file unless the --core-file option is specified either on the command line or in my.cnf.
Since --core-file is off by defaut, there would be no way to create a core file for the xtrabackup binary in PXB 2.2.5+. Which means the option should either be hardcoded to 'on', or be recognized by the xtrabackup binary so users have a choice. I prefer the latter.
Related branches
lp:~akopytov/percona-xtrabackup/bug1373429
- Alexey Kopytov (community): Approve
-
Diff: 68 lines (+24/-5)1 file modifiedstorage/innobase/xtrabackup/src/xtrabackup.cc (+24/-5)
| description: | updated |
Revision history for this message
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #1 |
To post a comment you must log in.
Percona now uses JIRA for bug reports so this bug report is migrated to: https:/