Re: Win32 hard crash problem

From: Michael Paesold <mpaesold(at)gmx(dot)at>
To: Magnus Hagander <mha(at)sollentuna(dot)net>
Cc: Dave Cramer <pg(at)fastcrypt(dot)com>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Merlin Moncure <mmoncure(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Win32 hard crash problem
Date: 2006-09-06 08:11:13
Message-ID: 44FE82A1.5070705@gmx.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Magnus Hagander wrote:
> Another point that at least I don't know - what kind of connection pool
> is it? Is it an external one (like pgpool) to which the java app
> connects (using FE/BE protocol, emulating a "proper postmaster" but
> pooling access to the database), or is it running inside the app server
> (like for example .net connection pooling does, which simply means that
> when you run the Open() method on the connection object it will pick
> something off an *internal* pool)?

Googling for 3CPO [1] shows that it is a Java-based connection pool that
implements connection pooling using the JDBC API, i.e. it is an *internal*
pool running inside the app servers JVM. PG Admin cannot in any case
connect through this pool.

Best Regards
Michael Paesold

[1] http://sourceforge.net/projects/c3p0

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Gavin Sherry 2006-09-06 08:13:37 Re: pgsql: Fix compiler warnings on 64-bit boxes:
Previous Message Teodor Sigaev 2006-09-06 08:05:41 Re: pgsql: Fix compiler warnings on 64-bit boxes: