From: Jim C. Nasby <decibel@decibel.org>
To: Matt Clark <matt@ymogen.net>
Cc: Postgresql Performance <pgsql-performance@postgresql.org>
Subject: Re: Caching of Queries
Date: Fri, 1 Oct 2004 10:13:03 -0500
Message-ID: <20041001151303.GU1297@decibel.org> (raw)
In-Reply-To: <415CEE8E.8060805@ymogen.net>
References: <00e801c4a4b6$5526dd30$8300a8c0@solent>
<1096306670.40463.173.camel@jester>
<41587867.4090505@ymogen.net>
<20040930221107.GP1297@decibel.org>
<415CEE8E.8060805@ymogen.net>
On Fri, Oct 01, 2004 at 06:43:42AM +0100, Matt Clark wrote:
>
> >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.
> >
> >
> Hmm, a question of definition - there's a difference between a pool and
> a persistent connection. Pretty much all web apps have one connection
> per process, which is persistent (i.e. not dropped and remade for each
> request), but not shared between processes, therefore not pooled.
OK, that'd work too... the point is if you're re-connecting all the time
it doesn't really matter what else you do for performance.
--
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
Subject: Re: Caching of Queries
In-Reply-To: <20041001151303.GU1297@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