Re: Implementing RESET CONNECTION ...

Oliver Jowett <oliver@opencloud.com>

From: Oliver Jowett <oliver@opencloud.com>

To: Hans-Jürgen Schönig <postgres@cybertec.at>

Cc: Karel Zak <zakkr@zf.jcu.cz>, Tom Lane <tgl@sss.pgh.pa.us>, Kris Jurka <books@ejurka.com>, eg@cybertec.at, List pgsql-patches <pgsql-patches@postgreSQL.org>

Date: 2005-01-04T12:36:16Z

Lists: pgsql-hackers

Hans-Jürgen Schönig wrote:

> If the JDBC driver prefers different behaviour (maybe for prepared 
> statements) we should discuss further options for RESET.
> Now there is: RESET CONNECTION (cleaning entire connection), RESET ALL 
> (cleaning GUCS only) and RESET some_guc.
> Maybe we want RESET LISTENER, RESET PREPARED, RESET CURSORS.
> Personally I think this is not a good idea.

It doesn't help, either, if user code can still issue RESET CONNECTION. 
(the scenario is user code, not the driver itself, originating the RESET..)

-O