Kevin Grittner wrote:
> I searched to ensure that nothing was invoking the Statement.setQueryTimeout method.
setQueryTimeout() is a no-op anyway in current drivers. I was talking
about the server's statement_timeout setting (set in postgresql.conf or
via SET or on a per-user/db basis).
> Hypothetically, would such a bug most likely be strictly server-side (in which case this is the wrong forum to pursue it)
Yes.
-O