Re: UNION and rows improperly unified: query optimization question - Mailing list pgsql-sql

From Tom Lane
Subject Re: UNION and rows improperly unified: query optimization question
Date
Msg-id 18659.1013476702@sss.pgh.pa.us
Whole thread Raw
In response to UNION and rows improperly unified: query optimization question  (Henry House <hajhouse@houseag.com>)
List pgsql-sql
Henry House <hajhouse@houseag.com> writes:
> So I run two select and combine them
> using a union statement, but this improperly combines two gl_entry lines th=
> at
> do not differ in amount or transaction ID.

AFAICT you do not want duplicate-row elimination at all.  Why don't you
use UNION ALL?
        regards, tom lane


pgsql-sql by date:

Previous
From: Henry House
Date:
Subject: UNION and rows improperly unified: query optimization question
Next
From: "Unnikrishnan Menon"
Date:
Subject: Re: Oracle "Jobs" in PostgreSQL