Re: Optimization via explicit JOINs - Mailing list pgsql-sql

From David Olbersen
Subject Re: Optimization via explicit JOINs
Date
Msg-id Pine.LNX.4.31.0103091757140.7941-100000@bubbles.electricutopia.net
Whole thread Raw
In response to Re: Optimization via explicit JOINs  (Stephan Szabo <sszabo@megazone23.bigpanda.com>)
Responses Re: Optimization via explicit JOINs  (Stephan Szabo <sszabo@megazone23.bigpanda.com>)
Re: Optimization via explicit JOINs  (Stephan Szabo <sszabo@megazone23.bigpanda.com>)
List pgsql-sql
On Fri, 9 Mar 2001, Stephan Szabo wrote:

->As a question, how many rows does
->select * from playlist p join songs s using (song_id) where
->p.waiting=TRUE;
->actually result in?

Well it depends. Most of the time that playlist table is "empty" (no rows where
waiting = TRUE), however users can (in a round about way) insert into that
table, so that there could be anywhere from 10, to 2,342, to more.

Why do you ask?

(The reason those plans chose 14 was because, at the time, there were 14 rows in
playlist)

-- Dave



pgsql-sql by date:

Previous
From: Stephan Szabo
Date:
Subject: Re: Optimization via explicit JOINs
Next
From: Stephan Szabo
Date:
Subject: Re: Optimization via explicit JOINs