Vladimir Sitnikov

This change will break sending streams in simple query mode. I guess we need to make this conditional and emit the stream in case it actually sends a simple query

Closing in favour of https://github.com/pgjdbc/pgjdbc/pull/3369

>from the JDBC API user's point of view, this change does not seem to be breaking The setting changes the behaviour of `java.sql.Statement#executeBatch`. The method should return then number of...

@beanww , can flink use `getObject(..., LocalDateTime.class)` instead of `getTimestamp(...)`?

@Sanne , can you please double-check you shared the right profiling results? I am afraid the file does not contain the traces of async-profiler data. --- > For example, I...

> At first impression I'm not really sure I sympatise with a user expecting a very specific behaviour from a concurrent, uncoordinated call to getWarnings ? The thing is pgjdbc...

> if you prefer - would you want to suggest exact settings you'd want to see? Frankly, I would love to see "all the backtraces for `ResourceLock`" to analyze what...

Apparently, the major part of `ResourceLock` overhead comes from * `org.postgresql.core.QueryExecutorBase#setTransactionState` (we could make a private variation that does not grab the lock) * `LruCache.borrow/put`

By the way, >https://github.com/TechEmpower/FrameworkBenchmarks/wiki/Project-Information-Framework-Tests-Overview#general-test-requirements > All test implementations **should be production-grade**. The particulars of this will vary by framework and platform, but the general sentiment is that the code and...

@anatoly-spb , thanks for the ping. I am afraid the current PR implementation lacks tests, so we can't ship it yet. Do you think you could help contributing tests for...