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
