pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Josh Berkus <josh@agliodbs.com>
To: pgsql-performance@postgresql.org
Cc: Tatsuo Ishii <t-ishii@sra.co.jp>
Subject: Re: PgPool changes WAS: PostgreSQL clustering VS MySQL clustering
Date: Mon, 24 Jan 2005 09:52:40 -0800
Message-ID: <200501240952.40183.josh@agliodbs.com> (raw)
In-Reply-To: <20050124.103033.21930526.t-ishii@sra.co.jp>
References: <200501210947.53938.josh@agliodbs.com>
	<200501231442.52830.josh@agliodbs.com>
	<20050124.103033.21930526.t-ishii@sra.co.jp>

Tatsuo,

> > Depends on your connection pooling software, I suppose.  Most connection
> > pooling software only returns connections to the pool after a user has
> > been inactive for some period ... generally more than 3 seconds.  So
> > connection continuity could be trusted.
>
> Not sure what you mean by "most connection pooling software", but I'm
> sure that pgpool behaves differently.

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.

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.

-- 
Josh Berkus
Aglio Database Solutions
San Francisco



view thread (8+ messages)  latest in thread

Message-ID: <200501240952.40183.josh@agliodbs.com>
Permalink:  ../200501240952.40183.josh@agliodbs.com/
Also on:    postgresql.org/message-id/200501240952.40183.josh@agliodbs.com

 · 

reply

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: josh@agliodbs.com, t-ishii@sra.co.jp
  Subject: Re: PgPool changes WAS: PostgreSQL clustering VS MySQL clustering
  In-Reply-To: <200501240952.40183.josh@agliodbs.com>

* 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