From: Joseph Shraibman <jks@selectacast.net>
To: Stephan Szabo <sszabo@megazone.bigpanda.com>
To: pgsql-performance@postgresql.org
Subject: Re: two seperate queries run faster than queries ORed together
Date: Mon, 22 Mar 2004 14:40:04 -0500
Message-ID: <405F4114.5070602@selectacast.net> (raw)
In-Reply-To: <20040322113002.D62908@megazone.bigpanda.com>
References: <c3d3sm$fdg$1@news.hub.org>
<200403221655.28667.dev@archonet.com>
<405F2893.5090805@selectacast.net>
<6875.1079979859@sss.pgh.pa.us>
<405F37CE.9070302@selectacast.net>
<20040322113002.D62908@megazone.bigpanda.com>
Stephan Szabo wrote:
> On Mon, 22 Mar 2004, Joseph Shraibman wrote:
>
>
>>Tom Lane wrote:
>>
>>>Joseph Shraibman <jks@selectacast.net> writes:
>>>
>>>
>>>>No, pkey is not the primary key in this case. The number of entries in u
>>>>that have pkey 260 and not boolfield is 344706.
>>>
>>>
>>>... and every one of those rows *must* be included in the join input,
>>
>>*If* you use one big join in the first place. If postgres ran the query
>>to first get the values with status == 3 from u, then ran the query to
>>get the entries from d, then combined them, the result would be the same
>>but the output faster. Instead it is doing seq scans on both tables and
>
>
> Well, you have to be careful on the combination to not give the wrong
> answers if there's a row with u.status=3 that matches a row d.status=3.
Right you would have to avoid duplicates. The existing DISTINCT code
should be able to handle that.
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-performance@postgresql.org
Cc: jks@selectacast.net, sszabo@megazone.bigpanda.com
Subject: Re: two seperate queries run faster than queries ORed together
In-Reply-To: <405F4114.5070602@selectacast.net>
* 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