Long story short: it might be nice to decouple pgjdbc from requiring DateStyle=ISO, however, it does not look like a walk in the park to me.
It looks like options come after DateStyle.
---
For historical reasons, pgjdbc often sends timestamps and dates as text-encoded literals, so it needs the backend to recognize the value properly.
The reason is that Java's `setTimestamp()` does not distinguish between timestamp and timestamptz, so the driver can't use Oid for timestamp/timestamptz,
so it falls back to text encoding with Oid "unknown".
I have not explored if the server would parse the timestamps appropriately.
---
At the same time, DateStyle might affect text representation of the timestamps, and the driver is not prepared to parse various flavours of timestamp representation.
A way out might be to make sure pgjdbc always requires binary encoding when receiving timestamp/timestamptz/date.
However, it might be trickier when processing arrays or structs as requiring all the arrays and structs to be in binary would take a bit of time as well.
