| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Radosław Smogura <rsmogura(at)softperience(dot)eu> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, David Fetter <david(at)fetter(dot)org>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, PG Hackers <pgsql-hackers(at)postgresql(dot)org>, PostgreSQL JDBC List <pgsql-jdbc(at)postgresql(dot)org>, robertmhaas(at)gmail(dot)com |
| Subject: | Re: [JDBC] Support for JDBC setQueryTimeout, et al. |
| Date: | 2010-10-15 14:23:27 |
| Message-ID: | 19979.1287152607@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-jdbc |
=?UTF-8?Q?Rados=C5=82aw_Smogura?= <rsmogura(at)softperience(dot)eu> writes:
> On Fri, 15 Oct 2010 10:37:05 +0200, Magnus Hagander <magnus(at)hagander(dot)net>
> wrote:
>>> But... connection pooler will not send RESET ALL in some situations,
>> To me, that sounds like a bug in the connection pooler. It is only
>> safe under quite limited circumstances.
> It's hard to say this is bug.
No it isn't. What you've described is a broken, unsafe, insecure pooler
that could not under any circumstances be recommended for general
purpose use. It might be okay if you trust all the clients to cooperate
completely, and to not have any bugs that might cause them to release a
connection while it's in a non-default state.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-10-15 14:27:20 | Re: Re: starting to review the Extend NOT NULL representation to pg_constraint patch |
| Previous Message | Stephen Frost | 2010-10-15 14:21:26 | Re: [JDBC] Support for JDBC setQueryTimeout, et al. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-10-15 14:38:54 | Re: [JDBC] Support for JDBC setQueryTimeout, et al. |
| Previous Message | Stephen Frost | 2010-10-15 14:21:26 | Re: [JDBC] Support for JDBC setQueryTimeout, et al. |