From: Matt Clark <matt@ymogen.net>
To: Jim C. Nasby <decibel@decibel.org>
Cc: Postgresql Performance <pgsql-performance@postgresql.org>
Subject: Re: Caching of Queries
Date: Fri, 01 Oct 2004 06:43:42 +0100
Message-ID: <415CEE8E.8060805@ymogen.net> (raw)
In-Reply-To: <20040930221107.GP1297@decibel.org>
References: <00e801c4a4b6$5526dd30$8300a8c0@solent>
<1096306670.40463.173.camel@jester>
<41587867.4090505@ymogen.net>
<20040930221107.GP1297@decibel.org>
>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.
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: matt@ymogen.net, decibel@decibel.org
Subject: Re: Caching of Queries
In-Reply-To: <415CEE8E.8060805@ymogen.net>
* 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