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 65EEC329EAD for ; Mon, 27 Sep 2004 22:38:36 +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 54487-04 for ; Mon, 27 Sep 2004 21:38:16 +0000 (GMT) Received: from bayswater1.ymogen.net (host-154-240-27-217.pobox.net.uk [217.27.240.154]) by svr1.postgresql.org (Postfix) with ESMTP id 4216D329E93 for ; Mon, 27 Sep 2004 22:38:17 +0100 (BST) Received: from [82.68.132.233] (82-68-132-233.dsl.in-addr.zen.co.uk [82.68.132.233]) by bayswater1.ymogen.net (Postfix) with ESMTP id 7DCCC9EAA1; Mon, 27 Sep 2004 22:38:16 +0100 (BST) Message-ID: <415887AE.6070909@ymogen.net> Date: Mon, 27 Sep 2004 22:35:42 +0100 From: Matt Clark User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Rod Taylor Cc: 'Aaron Werman' , 'Scott Kirkwood' , Postgresql Performance Subject: Re: Caching of Queries References: <00e801c4a4b6$5526dd30$8300a8c0@solent> <1096306670.40463.173.camel@jester> <41587867.4090505@ymogen.net> <1096317453.40463.226.camel@jester> In-Reply-To: <1096317453.40463.226.camel@jester> Content-Type: multipart/alternative; boundary="------------000803080104020300080009" X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.5 tagged_above=0.0 required=5.0 tests=HTML_MESSAGE, HTML_TITLE_EMPTY X-Spam-Level: X-Archive-Number: 200409/299 X-Sequence-Number: 8427 This is a multi-part message in MIME format. --------------000803080104020300080009 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit >>More to the point though, I think this is a feature that really really >>should be in the DB, because then it's trivial for people to use. >> >> > >How does putting it into PGPool make it any less trivial for people to >use? > The answers are at http://www2b.biglobe.ne.jp/~caco/pgpool/index-e.html . Specifically, it's a separate application that needs configuration, the homepage has no real discussion of the potential pitfalls of pooling and what this implementation does to get around them, you get the idea. I'm sure it's great software, but it doesn't come as part of the DB server, so 95% of people who would benefit from query caching being implemented in it never will. If it shipped with and was turned on by default in SUSE or RedHat that would be a different matter. Which I realise makes me look like one of those people who doesn't appreciate code unless it's 'popular', but I hope I'm not *that* bad... Oh OK, I'll say it, this is a perfect example of why My*** has so much more mindshare. It's not better, but it sure makes the average Joe _feel_ better. Sorry, I've got my corporate hat on today, I'm sure I'll feel a little less cynical tomorrow. M --------------000803080104020300080009 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit
More to the point though, I think this is a feature that really really 
should be in the DB, because then it's trivial for people to use.  
    

How does putting it into PGPool make it any less trivial for people to
use?
The answers are at  http://www2b.biglobe.ne.jp/~caco/pgpool/index-e.html .  Specifically, it's a separate application that needs configuration, the homepage has no real discussion of the potential pitfalls of pooling and what this implementation does to get around them, you get the idea.  I'm sure it's great software, but it doesn't come as part of the DB server, so 95% of people who would benefit from query caching being implemented in it never will.  If it shipped with and was turned on by default in SUSE or RedHat that would be a different matter.  Which I realise makes me look like one of those people who doesn't appreciate code unless it's 'popular', but I hope I'm not *that* bad...

Oh OK, I'll say it, this is a perfect example of why My*** has so much more mindshare.  It's not better, but it sure makes the average Joe _feel_ better.  Sorry, I've got my corporate hat on today, I'm sure I'll feel a little less cynical tomorrow.

M
--------------000803080104020300080009--