> On Thu, 29 Apr 2004, Tatsuo Ishii wrote:
> > > > Depending on your web development environment (java, php, .NET) etc,
> > > > you should be able to use some mechanism that will provide a pool of
> > > > connections to the database. Each request does not open a new
> > > > connection (and then release it), but insteads gets a connection from
> > > > the pool to use, and returns it back to the pool when done.
> > >
> > > Where can I find some examples for connection pooling with php? Or must I
> > > just use persistence connections?
> > Use pgpool
> > (ftp://ftp.sra.co.jp/pub/cmd/postgres/pgpool/pgpool-1.1.tar.gz).
> Tatsuo, I just tried pgpool (not replication yet) and noticed warnings appear
> in pgsql.log:
> (I just changed port number in my perl script to 9999)
> Apr 29 19:19:59 mira postgres: [4-1] WARNING: there is no transaction in progress
It's harmless. pgpool issues "ABORT" and "RESET ALL" to backend each
time when client connects to pgpool with pooled connection. This is
neccesary since previos client might disconnect to pgpool without
closing his/her transaction.
In response to
pgsql-general by date
|Next:||From: Bruce Momjian||Date: 2004-04-30 01:54:08|
|Subject: Re: postgresql idle|
|Previous:||From: Tom Lane||Date: 2004-04-30 00:30:49|
|Subject: Re: locking question |