>>> I think that it may break --no-vacuum, and I thought that there may be
>>> other option which remove things, eventually. Also, having a NO-OP looks
>>> ok to me.
>>
>> As far as I read the code, checkInitSteps() checks the initialization
>> steps that users specified. The initialization steps string that
>> "v" was replaced with blank character is not given to checkInitSteps().
>> So ISTM that dropping the handling of blank character from
>> checkInitSteps() doesn't break --no-vacuum.
>>
> This is a patch which does not allow space character in -I options .
I do not think that this is desirable. It would be a regression, and
allowing a no-op is not an issue in anyway.
--
Fabien Coelho - CRI, MINES ParisTech
