X-Original-To: pgsql-performance@postgresql.org Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 74E7C4762C8 for ; Fri, 31 Jan 2003 13:43:33 -0500 (EST) Received: from davinci.ethosmedia.com (unknown [209.10.40.251]) by postgresql.org (Postfix) with ESMTP id D4EDD475FD9 for ; Fri, 31 Jan 2003 13:43:32 -0500 (EST) Received: from [66.219.92.2] (HELO chocolate-mousse) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.0.2) with ESMTP id 2815030; Fri, 31 Jan 2003 10:42:52 -0800 Content-Type: text/plain; charset="iso-8859-1" From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: Jeff , pgsql-performance@postgresql.org Subject: Re: One large v. many small (fwd) Date: Fri, 31 Jan 2003 10:44:00 -0800 X-Mailer: KMail [version 1.4] References: In-Reply-To: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200301311044.00583.josh@agliodbs.com> X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200301/404 X-Sequence-Number: 1051 Jeff, > so after a week of engineering and futzing we had things under control.. > (db changes, massive app changes (agressive caching)) >=20 > Yes it was horrid to throw out RI (which caused some minor issues > later) but when the business is riding on it.. you make it work any way > you can. In a perfect world I would have done it another way, but when > the site is down (read: your business is not running, you are losing large > amounts of money) you need to put on your fire fighter suit, not your lab > coat. Actually, I'd say this is a great example of what I'm advocating. You=20 started out with a "correct" design, from an RDBMS perspective, and=20 compromised on it only when the performance issues became insurmountable.= =20=20 That sounds like a good approach to me. --=20 -Josh Berkus Aglio Database Solutions San Francisco