Re: connection pooling for postgres

Поиск
Список
Период
Сортировка
От Dave Cramer
Тема Re: connection pooling for postgres
Дата
Msg-id DDFFB849-8615-438C-973B-9C28B99D261C@fastcrypt.com
обсуждение исходный текст
Ответ на Re: connection pooling for postgres  ("Ido M. Tamir" <tamir@imp.univie.ac.at>)
Список pgsql-jdbc
This is another good option.

On 11-Jan-07, at 10:21 AM, Ido M. Tamir wrote:

> On Thursday 11 January 2007 15:28, James Neff wrote:
>> Greetings,
>
>> Where can I find good instructions or a tutorial on how to do
>> connection
>> pooling for JDBC to a Postgres database on my client?
>
> http://www.mchange.com/projects/c3p0/index.html
>
> c3p0 was designed to be butt-simple to use. Just put the jar file
> [lib/c3p0-0.9.0.jar] in your application's effective CLASSPATH, and
> make a
> DataSource like this:
>
> import com.mchange.v2.c3p0.*;
>
> ...
>
> ComboPooledDataSource cpds = new ComboPooledDataSource();
> cpds.setDriverClass( "org.postgresql.Driver" ); //loads the jdbc
> driver
> cpds.setJdbcUrl( "jdbc:postgresql://localhost/testdb" );
> cpds.setUser("dbuser");
> cpds.setPassword("dbpassword");
>
> [Optional] If you want to turn on PreparedStatement pooling, you
> must also set
> maxStatements and/or maxStatementsPerConnection(both default to 0):
>
> cpds.setMaxStatements( 180 );
>
>  Do whatever you want with your DataSource, which will be backed by a
> Connection pool set up with default parameters. You can bind the
> DataSource
> to a JNDI name service, or use it directly, as you prefer.
>  When you are done, you can clean up the DataSource you've created
> like this:
>
> DataSources.destroy( cpds );
>
>  That's it! The rest is detail.
>
> hth
> ido
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
>                http://archives.postgresql.org
>


В списке pgsql-jdbc по дате отправления:

Предыдущее
От: "Ido M. Tamir"
Дата:
Сообщение: Re: connection pooling for postgres
Следующее
От: Dave Cramer
Дата:
Сообщение: Re: connection pooling for postgres