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 1EB2A3A45FB for ; Thu, 6 Jan 2005 17:36:08 +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 25737-05 for ; Thu, 6 Jan 2005 17:35:43 +0000 (GMT) Received: from net2.micro-automation.com (net2.micro-automation.com [64.7.141.29]) by svr1.postgresql.org (Postfix) with SMTP id A170A3A47FC for ; Thu, 6 Jan 2005 17:35:42 +0000 (GMT) Received: (qmail 31984 invoked from network); 6 Jan 2005 17:35:12 -0000 Received: from dcdsl.ebox.com (HELO ?192.168.1.36?) (davec@64.7.143.116) by net2.micro-automation.com with SMTP; 6 Jan 2005 17:35:12 -0000 Message-ID: <41DD76E5.1090806@fastcrypt.com> Date: Thu, 06 Jan 2005 12:35:33 -0500 From: Dave Cramer Reply-To: pg@fastcrypt.com Organization: Postgres International User-Agent: Mozilla Thunderbird 1.0 (X11/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Frank Wiles Cc: Josh Berkus , pgsql-performance@postgresql.org Subject: Re: Low Performance for big hospital server .. References: <1104831107.41da6283add0c@webmail.moph.go.th> <1104939342.41dc094ecb1cf@webmail.moph.go.th> <758d5e7f050106041510f07dc5@mail.gmail.com> <200501060906.55832.josh@agliodbs.com> <20050106111207.52e39d04.frank@wiles.org> In-Reply-To: <20050106111207.52e39d04.frank@wiles.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.007 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200501/70 X-Sequence-Number: 9760 Reading can be worse for a normalized db, which is likely what the developers were concerned about. One always have to be careful to measure the right thing. Dave Frank Wiles wrote: >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 > > > > -- Dave Cramer http://www.postgresintl.com 519 939 0336 ICQ#14675561