From: Tatsuo Ishii <t-ishii@sra.co.jp>
To: matt@ymogen.net
Cc: pg@rbt.ca
Cc: awerman2@hotmail.com
Cc: scottakirkwood@gmail.com
Cc: pgsql-performance@postgresql.org
Subject: Re: Caching of Queries
Date: Thu, 07 Oct 2004 10:08:47 +0900 (JST)
Message-ID: <20041007.100847.26272104.t-ishii@sra.co.jp> (raw)
In-Reply-To: <012501c4aaf0$f12d0930$8300a8c0@solent>
References: <20041004.002823.85416338.t-ishii@sra.co.jp>
<012501c4aaf0$f12d0930$8300a8c0@solent>
> > I don't know what you are exactly referring to in above URL
> > when you are talking about "potential pitfalls of pooling".
> > Please explain more.
>
> Sorry, I wasn't implying that pgpool doesn't deal with the issues, just that
> some people aren't necessarily aware of them up front. For instance, pgpool
> does an 'abort transaction' and a 'reset all' in lieu of a full reconnect
> (of course, since a full reconnect is exactly what we are trying to avoid).
> Is this is enough to guarantee that a given pooled connection behaves
> exactly as a non-pooled connection would from a client perspective? For
> instance, temporary tables are usually dropped at the end of a session, so a
> client (badly coded perhaps) that does not already use persistent
> connections might be confused when the sequence 'connect, create temp table
> foo ..., disconnect, connect, create temp table foo ...' results in the
> error 'Relation 'foo' already exists'.
First, it's not a particular problem with pgpool. As far as I know any
connection pool solution has exactly the same problem. Second, it's
easy to fix if PostgreSQL provides a functionarity such as:"drop all
temporary tables if any". I think we should implement it if we agree
that connection pooling should be implemented outside the PostgreSQL
engine itself. I think cores agree with this.
--
Tatsuo Ishii
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: t-ishii@sra.co.jp, matt@ymogen.net, pg@rbt.ca, awerman2@hotmail.com, scottakirkwood@gmail.com
Subject: Re: Caching of Queries
In-Reply-To: <20041007.100847.26272104.t-ishii@sra.co.jp>
References: <20041004.002823.85416338.t-ishii@sra.co.jp> <012501c4aaf0$f12d0930$8300a8c0@solent> <20041007.100847.26272104.t-ishii@sra.co.jp>
* 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