Hello,
When shrinking DB, there's a lot of extra info displayed.
Although it doesn't hurt when calling the program interactively, it generates a lot og logs when scheduling it on a (very) regular basis.
I plan to propose a PR for a '-q' (quiet) flag to not display the info messages in the shrink process.
First of all, any reason to refuse this?
So, practical question: can someone explain me the goal of the p() complex macro in Linux?
Why not using the same as in Windows (#define p printf)?
I plan to use '#define p if (!quiet) printf' and use p() for all printf that are not important.
Thanks for advising
Hello,
When shrinking DB, there's a lot of extra info displayed.
Although it doesn't hurt when calling the program interactively, it generates a lot og logs when scheduling it on a (very) regular basis.
I plan to propose a PR for a '-q' (quiet) flag to not display the info messages in the shrink process.
First of all, any reason to refuse this?
So, practical question: can someone explain me the goal of the p() complex macro in Linux?
Why not using the same as in Windows (#define p printf)?
I plan to use '#define p if (!quiet) printf' and use p() for all printf that are not important.
Thanks for advising