Re: UNION and rows improperly unified: query optimization question

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Henry House <hajhouse(at)houseag(dot)com>
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: UNION and rows improperly unified: query optimization question
Date: 2002-02-12 01:18:22
Message-ID: 18659.1013476702@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

Henry House <hajhouse(at)houseag(dot)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

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message RPI 2002-02-12 01:33:14 help importing external excel file
Previous Message Tom Lane 2002-02-12 00:49:57 Re: RTLD_LAZY considered harmful (Re: pltlc and pltlcu