Re: [JDBC] Support for JDBC setQueryTimeout, et al.
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Cc: robertmhaas@gmail.com, david@fetter.org, pgsql-hackers@postgresql.org, pgsql-jdbc@postgresql.org, rsmogura@softperience.eu
Date: 2010-10-14T21:57:37Z
Lists: pgsql-hackers
"Kevin Grittner" <Kevin.Grittner@wicourts.gov> writes: > Robert Haas wrote: >> I thought we had decided on the client-side approach, but maybe >> I'm confused. I don't have a position one way or the other, just >> trying to understand the state of the conversation. > Well, I've been pretty vocal on supporting a client-side solution, > and Rados*aw clearly is in that camp, but that hardly makes a > consensus. David still has his patch out there, and Tom's comments > seemed to imply that he supports a solution involving the > statement_timeout GUC, so the question hardly seems settled. No, no, I was trying to point out some reasons why depending on statement_timeout would be problematic. I'm all for doing this client-side. regards, tom lane