From: | Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> |
---|---|
To: | bruce(at)momjian(dot)us |
Cc: | alvherre(at)commandprompt(dot)com, mweilguni(at)sime(dot)com, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: RESET CONNECTION? |
Date: | 2006-07-24 01:18:33 |
Message-ID: | 20060724.101833.57459762.t-ishii@sraoss.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Alvaro Herrera wrote:
> > Bruce Momjian wrote:
> > > Mario Weilguni wrote:
> > > > Will this patch make it into 8.2?
> > > > http://archives.postgresql.org/pgsql-patches/2004-12/msg00228.php
> > > >
> > > > It's a really nice feature, would be extremly useful with tools like pgpool.
> > >
> > > No, it will not because RESET CONNECTION can mess up interface code that
> > > doesn't want the connection reset. We are not sure how to handle that.
> >
> > Hmm, what interface code are you talking about?
>
> I believe JDBC, for example, sets things inside the interface that would
> be broken by RESET CONNECTION. Here is a thread about it:
>
> http://archives.postgresql.org/pgsql-patches/2005-01/msg00029.php
I think we had similar problem with client encoding and solved it by
using parameter status. Why don't we solve the JDBC problem in the
same way?
--
Tatsuo Ishii
SRA OSS, Inc. Japan
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-07-24 01:29:39 | Re: Sun Donated a Sun Fire T2000 to the PostgreSQL |
Previous Message | Robert Lor | 2006-07-24 01:00:31 | Re: [PATCHES] Generic Monitoring Framework with DTrace patch |