From: Jim C. Nasby <decibel@decibel.org>
To: Matt Clark <matt@ymogen.net>
Cc: Rod Taylor <pg@rbt.ca>
Cc: Aaron Werman <awerman2@hotmail.com>
Cc: Scott Kirkwood <scottakirkwood@gmail.com>
Cc: Postgresql Performance <pgsql-performance@postgresql.org>
Subject: Re: Caching of Queries
Date: Thu, 30 Sep 2004 17:11:07 -0500
Message-ID: <20040930221107.GP1297@decibel.org> (raw)
In-Reply-To: <41587867.4090505@ymogen.net>
References: <00e801c4a4b6$5526dd30$8300a8c0@solent>
<1096306670.40463.173.camel@jester>
<41587867.4090505@ymogen.net>
On Mon, Sep 27, 2004 at 09:30:31PM +0100, Matt Clark wrote:
> It's certainly the case that the typical web app (which, along with
> warehouses, seems to be one half of the needy apps), could probably do
> worse than use pooling as well. I'm not well up enough on pooling to
> know how bulletproof it is though, which is why I included it in my list
> of things that make me go 'hmm....'. It would be really nice not to
> have to take both things together.
If you're not using a connection pool of some kind then you might as
well forget query plan caching, because your connect overhead will swamp
the planning cost. This does not mean you have to use something like
pgpool (which makes some rather questionable claims IMO); any decent web
application language/environment will support connection pooling.
--
Jim C. Nasby, Database Consultant decibel@decibel.org
Give your computer some brain candy! www.distributed.net Team #1828
Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
FreeBSD: "Are you guys coming, or what?"
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: decibel@decibel.org, matt@ymogen.net, pg@rbt.ca, awerman2@hotmail.com, scottakirkwood@gmail.com
Subject: Re: Caching of Queries
In-Reply-To: <20040930221107.GP1297@decibel.org>
* 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