Tom Lisjac <netdxr@gmail.com> writes:
> We're in the process of deploying 9.2.1 to support an internal
> application we've been working on for the last few months. One of our
> programmers has recently complained that we get occasional hangs because
> "postgres automatically runs SELECT statements in a transaction that
> requires an explicit commit".
> That makes little sense and sounds like a dangling transaction, but in
> fairness I wanted to confirm that there isn't a set of defaults or flags
> that might cause the appearance of this behavior in version 9.
There's no such behavior in the server. If you're using any client
library above the level of libpq, it might be trying to be "helpful"
by managing transactions --- but you've not said what your client-side
programmming environment is, so it's hard to speculate about that.
regards, tom lane