X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id C94EBD1B2A6 for ; Thu, 10 Jun 2004 12:34:17 -0300 (ADT) 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 76775-10 for ; Thu, 10 Jun 2004 15:34:14 +0000 (GMT) Received: from web13801.mail.yahoo.com (web13801.mail.yahoo.com [216.136.175.11]) by svr1.postgresql.org (Postfix) with SMTP id 16322D1B1A5 for ; Thu, 10 Jun 2004 12:34:13 -0300 (ADT) Message-ID: <20040610153412.20577.qmail@web13801.mail.yahoo.com> Received: from [216.173.173.66] by web13801.mail.yahoo.com via HTTP; Thu, 10 Jun 2004 08:34:12 PDT Date: Thu, 10 Jun 2004 08:34:12 -0700 (PDT) From: Chris Gamache Reply-To: cgg007@yahoo.com Subject: CLUSTER strategy To: pgsql-admin@postgresql.org In-Reply-To: <24496.1086878464@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.9 tagged_above=0.0 required=5.0 tests=FROM_ENDS_IN_NUMS X-Spam-Level: X-Archive-Number: 200406/132 X-Sequence-Number: 13792 I need an informed opinion: The performance boost from clustering is wonderful. But, some tables would have to clustered several times a day, since there is usually some type of "status" column that is updated pretty regularly. Clustering is an expensive operation. If I pulled out that column into another "child" table and linked the tables by a foreign key to the "parent" I could update the "child" table and it wouldn't foul up the master table's ordering at all. Create a view on the two tables, and I'd have a relatively-stable setup as far as ordering goes, yes? Is this adviseable? In the long-run, will it yield the results that I expect? Did I miss any details? Should I be looking for any pitfalls? CG __________________________________ Do you Yahoo!? Friends. Fun. Try the all-new Yahoo! Messenger. http://messenger.yahoo.com/