Re: Overhead of union versus union all - Mailing list pgsql-general

From Alvaro Herrera
Subject Re: Overhead of union versus union all
Date
Msg-id 20090709200513.GO6414@alvh.no-ip.org
Whole thread Raw
In response to Overhead of union versus union all  (Tim Keitt <tkeitt@keittlab.org>)
Responses Re: Overhead of union versus union all
Re: Overhead of union versus union all
List pgsql-general
Tim Keitt wrote:
> I am combining query results that I know are disjoint. I'm wondering
> how much overhead there is in calling union versus union all. (Just
> curious really; I can't see a reason not to use union all.)

UNION needs to uniquify the output, for which it plasters an additional
sort step, whereas UNION ALL does not need to uniquify its output and
thus it can avoid the sort step.  Using UNION ALL is recommended
wherever possible.

--
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

pgsql-general by date:

Previous
From: Tim Keitt
Date:
Subject: Overhead of union versus union all
Next
From: Adam Rich
Date:
Subject: Re: Overhead of union versus union all