Implement option to suppress informational messages
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Triaged
|
Wishlist
|
Unassigned | ||
2.0 |
Won't Fix
|
Undecided
|
Unassigned | ||
2.1 |
Triaged
|
Wishlist
|
Unassigned | ||
2.2 |
Triaged
|
Wishlist
|
Unassigned | ||
2.3 |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
Xtrabackup prints information like:
[01] Copying ./mydatabase/
to STDERR instead of STDERR. Programs should allways write general-purpose output to STDOUT, and write warnings and errors to STDERR. This makes programs work well with the UNIX idioms, like pipes and crontab.
In example I wish to run a xtrabackup-script from crontab, and have crontab only send messages if warnings or error occur (by redirecting STDOUT to /dev/null). It might also be handy to use tools like "less" on the output.
It would be very nice to see this script updated to use STDOUT for informal messages, and STDERR for errors. It would provide much better flexibility, and co-operate well with other UNIX tools / UNIX environment.
affects: | percona-server → percona-xtrabackup |
Changed in percona-xtrabackup: | |
importance: | Low → Wishlist |
The behavior to write all diagnostic messages, both informational and errors, is intentional and has been implemented as a part of fixes for bug #733663 and bug #514068.
Streaming backups allow piping backup data to other utilities, which is another established UNIX idiom. Which means writing any messages to STDOUT would create a broken backup stream. It is similar to tar, for example, which writes all messages generated by the '-v' option to STDERR, even if they are not errors, for exactly the same reason: STDOUT may also be the archive destination.