Currently, slonik echos DDL being run via EXECUTE SCRIPT. This makes scripts very noisy and thus more difficult to identify success/fail status of a process from logs.
It would be great if slonik had a quiet mode, where its output was just your echo statements if things are working fine.
On failure, I'd like to see the slonik script output.
On failure I'd like to see failed DDL output.
This is useful if the scripts are being generated on the fly.
I'm not sure if this is better expressed by a single option or by a combination of options.
I wonder if this suggests having a 'status' that can be set.
cluster name = foo;
node 1 admin conninfo='something';
node 2 admin conninfo='something else';
execute script (stuff...);
execute script (more stuff...)
execute script (still more stuff...)
Adding a keyword or three like this is not terribly difficult; the question is of what they should control. If we have an answer that's relatively simple and which seems elegant, then it's likely a good answer. The above isn't quite that.
Actually, I suggest another approach...
When I modified DDL script processing, the printf() statements that you're observing were really part of my debugging infrastructure, when I was verifying that all was being handled properly.
It may be readily argued that these statements should simply be removed.
To that end, I have a branch that makes just such a change...
Minor patch involved:
This change looks fine to commit against master.
Committed to master: