Vladimir Sitnikov

That is not minutes. "initialize staging repository" could easily be one of the first actions, so wait time would be close to zero. Otherwise, spawning a job for the sake...

> Project name missing, Project description missing, Project URL missing, License information missing, SCM URL missing, Developer information missing It means the pom is not really valid. It is up...

Pretty sure it has not. The resolution would either use non-blocking API or use a separate thread to pump the data.

@stevenliang16 , do you think you can add a test for the change?

> Do you know if we have the mechanism to inject clock jump and network partition https://github.com/Devexperts/time-test + https://github.com/pgjdbc/pgjdbc/issues/898

What do you mean by `second`? https://github.com/pgjdbc/pgjdbc/search?q=enableSSL&type=

The PR is not yet merged, so its just one. The question here is to avoid multiple calls as PR is merged.

If this change is ever made, I think it makes sense to implement a kill flag. That is provide a flag to revert to previous value as I don't think...

Thanks for putting the fix together. However, I wonder what would be the behavior a) if the syntax does not match exactly. For instance `merge into ... using (select *...

I went through the changes, and I think they are good. I think it would be valuable to have the check on PR basis