On Tue, Mar 8, 2016 at 8:12 PM, Craig Ringer <craig@2ndquadrant.com> wrote: > There certainly are server/protocol frustrations.
I'm sympathetic to all of these and think we should work on fixing them, particularly...
> STRING TYPE ISSUES > --- > > PgJDBC can work around Pg's IMO somewhat overzealous type checks ...
This.
I've raised that multiple times and got nowhere. More importantly, I'm reasonably convinced that passing string types as UNKNOWNOID is what users generally want and expect anyway, and is consistent with what happens when you write string literals directly in SQL. I think we should just change PgJDBC to default to this already-optional behaviour, which is currently controlled by the stringtype=unspecified JDBC parameter.
Other drivers have similar issues, and can fix it the same way. Maybe we should document it somewhere, but I think this is in many ways the least deserving of attention. Partly because clients can work around it easily, partly because the energy input required for any change will be prohibitive and is better spent elsewhere.
I'd *much* rather have things like query cancel cookies, per-query GUCs at the protocol level, etc.
