X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 1A89932A259 for ; Fri, 1 Oct 2004 16:13:28 +0100 (BST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 56587-05 for ; Fri, 1 Oct 2004 15:13:10 +0000 (GMT) Received: from flake.decibel.org (flake.decibel.org [66.143.173.58]) by svr1.postgresql.org (Postfix) with ESMTP id 684A7329E79 for ; Fri, 1 Oct 2004 16:13:07 +0100 (BST) Received: by flake.decibel.org (Postfix, from userid 1001) id 580921C8B0; Fri, 1 Oct 2004 15:13:03 +0000 (GMT) Date: Fri, 1 Oct 2004 10:13:03 -0500 From: "Jim C. Nasby" To: Matt Clark Cc: Postgresql Performance Subject: Re: Caching of Queries Message-ID: <20041001151303.GU1297@decibel.org> References: <00e801c4a4b6$5526dd30$8300a8c0@solent> <1096306670.40463.173.camel@jester> <41587867.4090505@ymogen.net> <20040930221107.GP1297@decibel.org> <415CEE8E.8060805@ymogen.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <415CEE8E.8060805@ymogen.net> X-Operating-System: FreeBSD 4.10-RELEASE-p2 i386 X-Distributed: Join the Effort! http://www.distributed.net User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200410/6 X-Sequence-Number: 8482 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?"