X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 34BA3D1B8A2 for ; Wed, 8 Oct 2003 16:04:36 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 86414-04 for ; Wed, 8 Oct 2003 13:03:49 -0300 (ADT) Received: from davinci.ethosmedia.com (unknown [209.128.84.228]) by svr1.postgresql.org (Postfix) with ESMTP id C7452D1B8B0 for ; Wed, 8 Oct 2003 13:03:48 -0300 (ADT) Received: from [63.195.55.98] (HELO spooky) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.0.2) with ESMTP id 3741192; Wed, 08 Oct 2003 09:04:15 -0700 Content-Type: text/plain; charset="iso-8859-1" From: Josh Berkus Organization: Aglio Database Solutions To: Greg Spiegelberg , PgSQL Performance ML Subject: Re: Compare rows Date: Wed, 8 Oct 2003 09:01:45 -0700 User-Agent: KMail/1.4.3 References: <3F841A28.8060504@cranel.com> In-Reply-To: <3F841A28.8060504@cranel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200310080901.45093.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200310/213 X-Sequence-Number: 3961 Greg, > Anyone have any suggestions on how to efficiently compare > rows in the same table? This table has 637 columns to be > compared and 642 total columns. 637 columns? Are you sure that's normalized? It's hard for me to conceive of a circumstance where that many columns would be necessary. If this isn't a catastrophic normalization problem (which it sounds like), then you will probably still need to work through procedureal normalization code, as SQL simply doesn't offer any way around naming all the columns by hand. Perhaps you could describe the problem in more detail? -- Josh Berkus Aglio Database Solutions San Francisco