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 4C54A3A5780 for ; Tue, 25 Jan 2005 06:24:15 +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 89950-06 for ; Tue, 25 Jan 2005 06:24:01 +0000 (GMT) Received: from pillette.com (adsl-67-119-5-202.dsl.snfc21.pacbell.net [67.119.5.202]) by svr1.postgresql.org (Postfix) with ESMTP id 8D8453A586E for ; Tue, 25 Jan 2005 06:18:47 +0000 (GMT) Received: (from andrew@localhost) by pillette.com (8.11.6/8.11.6) id j0P6IBN19000; Mon, 24 Jan 2005 22:18:11 -0800 Date: Mon, 24 Jan 2005 22:18:11 -0800 From: andrew@pillette.com Message-Id: <200501250618.j0P6IBN19000@pillette.com> Subject: Re: poor performance of db? To: John Arbash Meinel Cc: SpaceBallOne , pgsql-performance@postgresql.org X-Originating-IP: 64.169.162.78 X-Mailer: Webmin 0.940 MIME-Version: 1.0 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.205 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO, NO_REAL_NAME X-Spam-Level: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Archive-Number: 200501/452 X-Sequence-Number: 10142 This is a multi-part message in MIME format. --bound1106633891 Content-Type: text/plain Content-Transfer-Encoding: 7bit I'm also an autodidact on DB design, although it's well more than a year now. If you are planning to clean up the design, I strongly suggest getting a visual tool. Google for something like "database design tool". Some are extremely expensive (e.g. ERwin, which I think is renamed having been bought out). There's a very cheap shareware one that I won't mention by name because it crashed my machine consistently. Right now I'm using "Case Studio", which has some very eccentric UI (no one enforced consistency of UI across modules, which is rather ironic in a design tool) but capable and user-extensible. ERwin's manual also had the best explanation of denormalization I've read, short and to the point. The ability to make schema revisions quickly lets me concentrate on *better-written queries* and *improved table definition* without having to overcome inertia. --bound1106633891--