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 3C3B93A4A4F; Thu, 6 Jan 2005 18:45:31 +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 39473-08; Thu, 6 Jan 2005 18:45:07 +0000 (GMT) Received: from tus-gate4.raytheon.com (tus-gate4.raytheon.com [199.46.245.233]) by svr1.postgresql.org (Postfix) with ESMTP id BFF143A4580; Thu, 6 Jan 2005 18:44:15 +0000 (GMT) Received: from ds02t00.directory.ray.com (ds02t00.directory.ray.com [147.25.154.117]) by tus-gate4.raytheon.com (8.12.10/8.12.10) with ESMTP id j06Ii8Lg027872; Thu, 6 Jan 2005 11:44:08 -0700 (MST) Received: from ds02t00 (localhost [127.0.0.1]) by ds02t00.directory.ray.com (Switch-3.1.4/Switch-3.1.0) with ESMTP id j06Ihi62021769; Thu, 6 Jan 2005 18:43:45 GMT Received: from ds02t00.directory.ray.com with LMTP by ds02t00 (2.0.6/sieved-2-0-build-559); Thu, 6 Jan 2005 18:43:44 +0000 Received: from notesserver5.ftw.us.ray.com (notesserver5.ftw.us.ray.com [151.168.145.35]) by ds02t00.directory.ray.com (Switch-3.1.4/Switch-3.1.0) with ESMTP id j06Ih1tm021471 sender Richard_D_Levine@raytheon.com; Thu, 6 Jan 2005 18:43:05 GMT Subject: Re: Low Performance for big hospital server .. To: Frank Wiles Cc: Josh Berkus , pgsql-performance@postgresql.org, pgsql-performance-owner@postgresql.org X-Mailer: Lotus Notes Release 5.0.8 June 18, 2001 Message-ID: From: Richard_D_Levine@raytheon.com Date: Thu, 6 Jan 2005 13:33:00 -0500 X-MIMETrack: Serialize by Router on NotesServer5/HDC(Release 6.5.2|June 01, 2004) at 01/06/2005 01:43:05 PM MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII X-SPAM: 0.00 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.181 tagged_above=0 required=5 tests=AWL, NO_REAL_NAME X-Spam-Level: X-Archive-Number: 200501/74 X-Sequence-Number: 9764 In my younger days I denormalized a database for performance reasons and have been paid for it dearly with increased maintenance costs. Adding enhanced capabilities and new functionality will render denormalization worse than useless quickly. --Rick Frank Wiles To: Josh Berkus Sent by: cc: pgsql-performance@postgresql.org pgsql-performance-owner@pos Subject: Re: [PERFORM] Low Performance for big hospital server .. tgresql.org 01/06/2005 12:12 PM On Thu, 6 Jan 2005 09:06:55 -0800 Josh Berkus wrote: > I can't tell you how many times I've seen this sort of thing. And > the developers always tell me "Well, we denormalized for performance > reasons ... " Now that's rich. I don't think I've ever seen a database perform worse after it was normalized. In fact, I can't even think of a situation where it could! --------------------------------- Frank Wiles http://www.wiles.org --------------------------------- ---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to majordomo@postgresql.org so that your message can get through to the mailing list cleanly