Re: BUG #6535: LEFT JOIN on large table is altering data

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Aren Cambre" <aren(at)arencambre(dot)com>
Cc: <pgsql-bugs(at)postgresql(dot)org>,"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: BUG #6535: LEFT JOIN on large table is altering data
Date: 2012-03-18 20:22:38
Message-ID: 4F65FDBE02000025000463D6@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Aren Cambre <aren(at)arencambre(dot)com> wrote:

> SELECT COUNT(*)
> FROM consistent.master
> WHERE citation_id IS NOT NULL
> UNION
> SELECT COUNT(*)
> FROM consistent.master
> UNION
> SELECT COUNT(*)
> FROM consistent.master
> WHERE citation_id IS NULL
>
> I got this result:
>
> 2085344
> 2085343
> 0
>
> Not clear how adding a WHERE clause, whose only practical effect
> is to reduce the number of rows returned, could cause *more* rows
> to be returned. That seems buggy to me.

Never assume that the rows will be returned in any particular order
from a query unless you specify ORDER BY. Assuming, as you seem to
be doing, that rows from the left side of a UNION will be output
before rows from the right side is not safe. You have no way of
knowing which row in a result set like that came from which of the
UNIONed SELECTs. In this case your assumption is almost certainly
wrong.

-Kevin

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Aren Cambre 2012-03-18 20:29:41 Re: BUG #6535: LEFT JOIN on large table is altering data
Previous Message Aren Cambre 2012-03-18 19:59:12 Re: BUG #6535: LEFT JOIN on large table is altering data