Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250]) by postgresql.org (8.11.3/8.11.4) with ESMTP id f8LNrGe94676 for ; Fri, 21 Sep 2001 19:53:16 -0400 (EDT) (envelope-from josh@agliodbs.com) Received: from [209.10.40.250] (account ) by davinci.ethosmedia.com (CommuniGate Pro WebUser 3.4.1) with HTTP id 123693; Fri, 21 Sep 2001 16:53:11 -0700 From: "Josh Berkus" Subject: Re: Q on "Re: select is fast, update based on same where clause is slow " To: Kovacs Baldvin Cc: pgsql-sql@postgresql.org X-Mailer: CommuniGate Pro Web Mailer v.3.4.1 Date: Fri, 21 Sep 2001 16:53:11 -0700 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Archive-Number: 200109/188 X-Sequence-Number: 4870 Bladvin, > I understand why did Jeff's original solution not work. I understand > why yours do. > > But could you please explain me how the 74000^2 can be calculated > for this original query?: Sure. In Jeff's original query, the updated instance of the table (sessions2) and the referenced instance (s) are seperate, without any JOIN or WHERE conditions to link them. Under these conditions, SQL engines do a CROSS JOIN, where every single one of the rows in the first table is matched against every single one of the rows in the second table. This gives you a result set of the number of rows in sessions2 * the number of rows in s. 74,000^2 Get it? Example: TableA: 1 A 2 B Table B 7 H 8 G SELECT * FROM TableA, TableB 1 A 7 H 1 A 8 G 2 B 7 H 2 B 8 G -Josh -Josh ______AGLIO DATABASE SOLUTIONS___________________________ Josh Berkus Complete information technology josh@agliodbs.com and data management solutions (415) 565-7293 for law firms, small businesses fax 621-2533 and non-profit organizations. San Francisco