Skip site navigation (1) Skip section navigation (2)

Re: [JDBC] Support for JDBC setQueryTimeout, et al.

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: <robertmhaas(at)gmail(dot)com>
Cc: <david(at)fetter(dot)org>,<pgsql-hackers(at)postgresql(dot)org>, <pgsql-jdbc(at)postgresql(dot)org>, <rsmogura(at)softperience(dot)eu>
Subject: Re: [JDBC] Support for JDBC setQueryTimeout, et al.
Date: 2010-10-14 17:25:13
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-jdbc
Robert Haas  wrote:
Kevin Grittner  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.
Regarding JDBC in the CF process -- other interfaces are handled
there.  I haven't seen one patch this size for JDBC since I've been
involved, let alone two competing patches to implement the same
feature.  Small patches which can be quickly handled don't make sense
to put into the process, but it seemed reasonable for these.


pgsql-hackers by date

Next:From: Robert HaasDate: 2010-10-14 17:29:58
Subject: Re: SQL command to edit postgresql.conf, with comments
Previous:From: Bruce MomjianDate: 2010-10-14 17:18:26
Subject: Re: A small update for postgresql.conf.sample

pgsql-jdbc by date

Next:From: Radosław SmoguraDate: 2010-10-14 18:40:57
Subject: Re: [JDBC] Support for JDBC setQueryTimeout, et al.
Previous:From: Patricia Rincon LopezDate: 2010-10-14 16:52:53
Subject: problema con password

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group