| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Merlin Moncure <mmoncure(at)gmail(dot)com>, Magnus Hagander <mha(at)sollentuna(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Win32 hard crash problem |
| Date: | 2006-09-05 22:34:36 |
| Message-ID: | 20060905223436.GV21195@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Joshua D. Drake wrote:
> Alvaro Herrera wrote:
> >Joshua D. Drake wrote:
> >>Alvaro Herrera wrote:
> >>>What I've been wondering all along is whether they are using a
> >>>connection pool.
> >>Yes they are using a connection pool. A java based one.
> >
> >It's quite possible that it's the connection pool that gets confused,
> >and not PostgreSQL itself. It would be interesting if they change the
> >connection setting when the "hang" next occurs, to point directly to
> >PostgreSQL bypassing the connection pool.
>
> Well except when they are connecting with Pgadmin (which wouldn't go
> through the connection pool) they get the error as well.
Are you assuming, or did they/you verify that this is indeed the case?
I see no reason to assume that pgAdmin can't connect via a pool.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-09-05 22:35:30 | Re: Win32 hard crash problem |
| Previous Message | Tom Lane | 2006-09-05 22:32:57 | Re: ISBN/ISSN/ISMN/EAN13 module |