Vladimir Sitnikov

>I can provide even more examples of problems if necessary It would be great. I would suggest we solve problem a time rather than combine everything possible within a single...

> testTypeOnDbSite_functionOverloading Currently it defines a function with `timestmaptz`, and a function with `text` parameters. I would suggest adding `timestamp` (without tz), `time`, and `timetz` into the mix and suggest...

I think this is ready, and I'm going to merge it after some time

The existing code was building SQL with StringBuilder, so I benchmarked SB only

Thank you for the PR, however, I am leaning towards a different implementation: 1. Refactor TypeCache code (see https://github.com/pgjdbc/pgjdbc/pull/3062) 2. Factor common types to a read-only part. In other words,...

Ultimately, I would like to hard-code well-known pg catalog entries for the current DB versions, so query catalog only in case we face an unknown type. WDYT?

>I don't see another way to do this. So yes It might be useful to have something like "global backend unique ID" returned on connect. If the backend could return...

The actual issue is that a single misbehaving replica might cause noticeable issues when creating connections. The most pronounced case is primary switchover. * Imagine there are 6 replicas and...

The issue is that the current implementation does not handle the case well, and it does not specify "please do not use it, use something else instead". So the users...

>An option might be to start an ExecutorService with 6 threads, test each replica in parallel? (something along the lines of testing the likely candidates in parallel) Fair point. Imagine...