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 42BED8B9B83 for ; Tue, 1 Feb 2005 21:01:18 +0000 (GMT) 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 12686-04 for ; Tue, 1 Feb 2005 21:01:02 +0000 (GMT) Received: from smtp0.libero.it (smtp0.libero.it [193.70.192.33]) by svr1.postgresql.org (Postfix) with ESMTP id 1EE528B9D15 for ; Tue, 1 Feb 2005 21:01:00 +0000 (GMT) Received: from localhost (172.16.1.79) by smtp0.libero.it (7.0.027-DD01) id 41BDA86900A98799; Tue, 1 Feb 2005 22:00:57 +0100 Received: from [62.98.81.87] (62.98.81.87) by smtp3.libero.it (7.0.027-DD01) (authenticated as tdezotti@inwind.it) id 41FF66430009F81D; Tue, 1 Feb 2005 22:00:57 +0100 Message-ID: <41FFEE02.3080605@streppone.it> Date: Tue, 01 Feb 2005 22:00:50 +0100 From: Cosimo Streppone User-Agent: Mozilla Thunderbird 0.9 (X11/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Merlin Moncure Cc: Postgresql Performance list Subject: Re: High end server and storage for a PostgreSQL OLTP system References: <6EE64EF3AB31D5448D0007DD34EEB3412A75FE@Herge.rcsinc.local> In-Reply-To: <6EE64EF3AB31D5448D0007DD34EEB3412A75FE@Herge.rcsinc.local> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at libero.it serv1 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200502/22 X-Sequence-Number: 10351 Merlin Moncure wrote: > Corollary: use pl/pgsql. It can be 10 times or more faster than query > by query editing. Merlin, thanks for your good suggestions. By now, our system has never used "stored procedures" approach, due to the fact that we're staying on the minimum common SQL features that are supported by most db engines. I realize though that it would provide an heavy performance boost. > You also have the parse/bind interface This is something I have already engineered in our core classes (that use DBI + DBD::Pg), so that switching to 8.0 should automatically enable the "single-prepare, multiple-execute" behavior, saving a lot of query planner processing, if I understand correctly. -- Cosimo