On Tue, 4 Jan 2005, [ISO-8859-1] Hans-Jürgen Schönig wrote:

> I completely agree with Karel. I think it is a bad idea to change the 
> protocol for such a minor feature - i tend to call it overkill.

I agree.  I don't think it's imperative to prevent or detect this 
condition.  The only real caller of this should be the driver itself.  If 
the end user does call this and breaks things I wouldn't consider it our 
problem.  Making this available at the protocol level only would certainly 
solve that, but it's not really compelling to make a protocol level jump.

> I want to add one point to this discussion: There is not just JDBC - 
> other connection pools or clients might want different behaviour (which 
> can from my point of view only lead to a complete reset).

Right, I am speaking from the JDBC driver perspective, but I think any 
higher level interface should desire to do statement pooling, which will 
have this problem.  You have not stated what client interface you are 
targetting, but I believe anything written to a higher level than libpq 
will need to be aware of this.  Perhaps -patches isn't the right place to 
solicit input for this.

Kris Jurka

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?


Reply via email to