| From: | Oliver Jowett <oliver(at)opencloud(dot)com> |
|---|---|
| To: | Hans-Jürgen Schönig <postgres(at)cybertec(dot)at> |
| Cc: | Karel Zak <zakkr(at)zf(dot)jcu(dot)cz>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Kris Jurka <books(at)ejurka(dot)com>, eg(at)cybertec(dot)at, List pgsql-patches <pgsql-patches(at)postgreSQL(dot)org> |
| Subject: | Re: Implementing RESET CONNECTION ... |
| Date: | 2005-01-04 12:36:16 |
| Message-ID: | 41DA8DC0.9040006@opencloud.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Buttafuoco | 2005-01-04 13:53:21 | Re: [ANNOUNCE] PostgreSQL 8.0.0 Release Candidate 3 |
| Previous Message | Oliver Jowett | 2005-01-04 12:33:16 | Re: Implementing RESET CONNECTION ... |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2005-01-04 14:49:45 | Re: psql session log |
| Previous Message | Oliver Jowett | 2005-01-04 12:33:16 | Re: Implementing RESET CONNECTION ... |