Received: from bubbles.electricutopia.net (bubbles.electricutopia.net [63.214.178.76]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f29NuZx43230 for ; Fri, 9 Mar 2001 18:56:36 -0500 (EST) (envelope-from dave@slickness.org) Received: from localhost (dave@localhost) by bubbles.electricutopia.net (8.9.3/8.9.3) with ESMTP id PAA06967; Fri, 9 Mar 2001 15:54:05 -0800 Date: Fri, 9 Mar 2001 15:54:05 -0800 (PST) From: David Olbersen X-X-Sender: To: Stephan Szabo cc: Subject: Re: Optimization via explicit JOINs In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Archive-Number: 200103/208 X-Sequence-Number: 1862 On Fri, 9 Mar 2001, Stephan Szabo wrote: -> Hmm, what were the two queries anyway? The "slower" query ---------------------------- SELECT to_char( p.insertion_time, 'HH:MI AM MM/DD' ) as time_in, s.name as title, a.name as artist, s.length as length FROM playlist p, songs s, artists a WHERE p.waiting = TRUE AND p.song_id = s.song_id AND s.artist_id = a.artist_id ORDER BY p.item_id The "faster" query ---------------------------- SELECT to_char( p.insertion_time, 'HH:MI AM MM/DD' ) as time_in, s.name as title, s.length as length, a.name as artist FROM playlist p JOIN songs s USING (song_id), artists a WHERE p.waiting = TRUE AND p.song_id = s.song_id AND s.artist_id = a.artist_id ORDER BY p.item_id; Notice how the only difference is in the FROM clause? -- Dave