X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id CC1FDD1E0D2 for ; Fri, 20 Feb 2004 20:24:40 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 34908-01 for ; Fri, 20 Feb 2004 16:24:33 -0400 (AST) Received: from out014.verizon.net (out014pub.verizon.net [206.46.170.46]) by svr1.postgresql.org (Postfix) with ESMTP id 502FAD1DFFE for ; Fri, 20 Feb 2004 16:24:31 -0400 (AST) Received: from spacemonkeylabs.com ([68.161.140.190]) by out014.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20040220202429.FOYR19064.out014.verizon.net@spacemonkeylabs.com>; Fri, 20 Feb 2004 14:24:29 -0600 Message-ID: <40366CFC.5050302@spacemonkeylabs.com> Date: Fri, 20 Feb 2004 15:24:28 -0500 From: Mitch Pirtle Organization: Spacemonkey Laboratories User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031115 Thunderbird/0.3 X-Accept-Language: en-us, en MIME-Version: 1.0 To: jer@highboard.com Cc: pgsql-admin@postgresql.org Subject: Re: PosgreSQL hogging resources? References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at out014.verizon.net from [68.161.140.190] at Fri, 20 Feb 2004 14:24:28 -0600 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200402/311 X-Sequence-Number: 12485 Jeremy Smith wrote: >I will look into some of the suggestions you have made, the problem is that >I can't do large scale optimization at the moment because I am still adding >features to the site. I just wonder if the best mode of attack would be >switching back to mysql until I have added all of the necessary features, >optimizing the queries and code there, and then switching back to pg at a >later date. > When you switch to pg, you will be able to move some/lots? of your code into the database as views, stored procedures, triggers etc... So keep that in mind while working in MySQL, as you will definitely need a different approach. I inherited a site that had very database-hungry pages, and started using stored procs and triggers to automate some of the jobs (like updates and such) in the database, instead of making the webserver manually send the instructions across the wire. If you plan on taking this approach then you should get your app into pg sooner than later... -- Mitch, wondering about 12 packs?