From: Ragnar Hafstaư <gnari@simnet.is>
To: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-performance@postgresql.org, Tatsuo Ishii <t-ishii@sra.co.jp>
Subject: Re: PgPool changes WAS: PostgreSQL clustering VS MySQL
Date: Mon, 24 Jan 2005 18:24:05 +0000
Message-ID: <1106591045.22635.7.camel@localhost.localdomain> (raw)
In-Reply-To: <200501240952.40183.josh@agliodbs.com>
References: <200501210947.53938.josh@agliodbs.com>
<200501231442.52830.josh@agliodbs.com>
<20050124.103033.21930526.t-ishii@sra.co.jp>
<200501240952.40183.josh@agliodbs.com>
On Mon, 2005-01-24 at 09:52 -0800, Josh Berkus wrote:
> [about keeping connections open in web context]
> Ah, clarity problem here. I'm talking about connection pooling tools from
> the client (webserver) side, such as Apache::DBI, PHP's pg_pconnect,
> Jakarta's connection pools, etc. Not pooling on the database server side,
> which is what pgPool provides.
note that these sometimes do not provide connection pooling as such,
just persistent connections (Apache::DBI)
> Most of these tools allocate a database connection to an HTTP/middleware
> client, and only release it after a specific period of inactivity. This
> means that you *could* count on "web-user==connection" for purposes of
> switching back and forth to the master -- as long as the connection-recycling
> timeout were set higher than the pgPool switch-off period.
no. you can only count on web-server-process==connection, but not
web-user==connection, unless you can garantee that the same user
client always connects to same web-server process.
am i missing something ?
gnari
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: gnari@simnet.is, josh@agliodbs.com, t-ishii@sra.co.jp
Subject: Re: PgPool changes WAS: PostgreSQL clustering VS MySQL
In-Reply-To: <1106591045.22635.7.camel@localhost.localdomain>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox