I created https://liquibase.jira.com/browse/CORE-1802 to track improvements to the logging. Liquibase should be providing feedback on what it is executing. We've not logged the return value of SQL but that would be worth logging as well.
There is updateSql mode that you can use to list the SQL that WILL run, but the change in 1802 would improve the logging during execution.
Liquibase would be able to log the rows updated according to the JDBC driver, but that is after-the-fact "X rows were changed" information. The forecasting support I mentioned is more around discovering what WILL be changed by a liquibase update.
Nathan