From: Tom Lane <tgl@sss.pgh.pa.us>
To: Scott Pederick <sql.postgresql.org@pederick.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: JOIN not being calculated correctly
Date: Sat, 20 Nov 2004 16:51:34 -0500
Message-ID: <626.1100987494@sss.pgh.pa.us> (raw)
In-Reply-To: <000501c4cf49$31c346e0$e1f9f4dc@boblaptop>
References: <001e01c4bc14$78cbda90$1d7af0dc@boblaptop>
<4187D611.2000109@ca.afilias.info>
<000501c4cf49$31c346e0$e1f9f4dc@boblaptop>
"Scott Pederick" <sql.postgresql.org@pederick.com> writes:
> Still can't fathom why it's not using an index scan on the jobs table..
Why exactly do you think that would make it faster?
The query evidently requires visiting every single jobs row, so a
seqscan seems appropriate to me; indeed I'd say the planner picked
exactly the perfect plan. If you think not, try forcing other plan
choices and see what happens to the runtime.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, sql.postgresql.org@pederick.com
Subject: Re: JOIN not being calculated correctly
In-Reply-To: <626.1100987494@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox