Re: [HACKERS] Oops, I seem to have changed UNION's behavior - Mailing list pgsql-hackers

From Taral
Subject Re: [HACKERS] Oops, I seem to have changed UNION's behavior
Date
Msg-id Pine.LNX.4.10.9905091551330.8677-100000@dragon.taral.net
Whole thread Raw
In response to Re: [HACKERS] Oops, I seem to have changed UNION's behavior  (Thomas Lockhart <lockhart@alumni.caltech.edu>)
List pgsql-hackers
On Sun, 9 May 1999, Thomas Lockhart wrote:

> > > Am I right in thinking that UNION (without ALL) is defined to do a
> > > DISTINCT on its result, so that duplicates are removed even if the
> > > duplicates both came from the same source table?  That's what 6.4.2
> > > does, but I do not know if it's strictly kosher according to the SQL
> > > spec.
> 
> Yes, this is the right behavior according to SQL92...

In which case something should put a DISTINCT on queries using UNION...
since making T_Query nodes never equal is a deoptimization.

Taral



pgsql-hackers by date:

Previous
From: Taral
Date:
Subject: Re: [HACKERS] inet data type regression test fails
Next
From: Thomas Lockhart
Date:
Subject: Re: [HACKERS] NUMERIC type conversions leave much to be desired