PostgreSQL union vs union all

Difference Between PostgreSQL union vs union all

PostgreSQL union: UNION operator in PostgreSQL is used to combine the result of two or more SELECT statements along with removing the duplicate rows. Before the final result of the UNION operation, DISTINCT is applied to the resultset, which removes the duplicate rows from it and displays only the relevant data to the user.

PostgreSQL union all: UNION ALL operator in PostgreSQL is also used to combine the result of two or more SELECT statements but it does not perform any additional operation on the resultset. Instead, it returns the full table just by concatenating the results of SELECT statements and displaying it as it is to the user.  It is somewhat faster than the UNION operator as no extra overhead of removing duplicates needs to be performed.

Head to Head Comparison Between PostgreSQL union vs union all (Infographics)

Below is the Top Comparison Between PostgreSQL union vs union all:

Key Differences

Some of the key differences between union and union all in PostgreSQL describing the detailed description are given below:

1. Both the UNION and UNION ALL operators are used in PostgreSQL to combine two tables by merging the rows returned by two or more SELECT statements. The only difference being that UNION does not return or removes the duplicate rows whereas UNION returns all the rows returned after merging, either duplicate or not.

2. The UNION operator performs the DISTINCT operation on the resultset, which means it removes the duplicate rows from it. So, in case of a large volume of data present in the tables, the UNION operator is considered to be slower than the UNION ALL operator as it hampers the overall speed by performing the additional overhead of the DISTINCT operation.

3. To perform both the UNION and UNION ALL operation for combining the tables, the same conditions need to be satisfied:

• The same number of columns should be retrieved from each SELECT statement which is to be combined.
• Columns retrieved from each SELECT statement must be of the same data type.
• Columns retrieved from each SELECT statement must be in the same order.

4. Let us understand the difference in the result set returned by the UNION and UNION ALL operator with the help of an example:

Consider the two tables with the name ‘ITDepartment’ and ‘OperationsDepartment’ having the fields ‘emp_id’ and ‘emp_name’

ITDepartment:

OperationsDepartment:

Query using UNION operator:

SELECT * from ITDepartment
UNION
SELECT *  from OperationsDepartment;

Result:

In the above tables, Employee ‘Gourang’ having emp_id ‘E_004’ is working in both IT and Operations Department so present in both the tables, i.e. ‘ITDepartment’ and ‘OperationsDepartment’. Since the UNION operator on the SELECT statement of both the tables returns a combined result set of both tables and removes the duplicate rows. So, performing the UNION on the resultset of both the tables, results displaying the employee ‘Gourang’ only once.

Query using UNION ALL operator:

SELECT * from ITDepartment
UNION ALL
SELECT *  from OperationsDepartment;

Result:

In the above tables, Employee ‘Gourang’ having emp_id ‘E_004’ is working in both IT and Operations Department so present in both the tables, i.e. ‘ITDepartment’ and ‘OperationsDepartment’. Since the UNION ALL operator on the SELECT statement of both the tables returns a combined result set of both tables but does not remove the duplicate rows instead displays all the data resulted by concatenation. So

performing the UNION  ALL on the resultset of both the tables, results displaying the employee ‘Gourang’ two times. If it is present ‘n’ number of times, UNION ALL will return all of them.

Comparison Table

Below given is the comparison table showing the head to head comparison between union and union all in PostgreSQL:

S.No.	PostgreSQL union	PostgreSQL union all
1.	Union operator in PostgreSQL combines the result set of two or more SELECT statements. Duplicate rows returned from the result of SELECT statements are eliminated first and then combined to give the unified result.	Union all operators in PostgreSQL combine the result of two or more SELECT statements without removing the duplicate rows returned from each SELECT.
2.	Union operator in PostgreSQL eliminates the duplicate rows returned by merging the two SELECT statements.	Union all operator does not remove the duplicate rows  (if present) in the result obtained by merging the two SELECT statements.
3.	In case of many duplicates, the union operator works great as it shows only the relevant data to the user.	Union all operator is slower than the union operator in case of a large number of duplicates resulting from querying as processing duplicates may exceed the query execution time.
4.	Sometimes, processing time gets slower in the case of union operators as there is an extra overhead of performing the DISTINCT on the result set.	In case of processing time, union all operator is faster as it does not removes the duplicate rows in the result set.
5.	Syntax of using the union operator in PostgreSQL is:   SELECT exp1, exp2, exp3, . . . from tab1 UNION SELECT exp1, exp2, exp3, . . . from tab2   Where, exp1, exp2, exp3, . . . are the column names that need to be retrieved from tab1 and tab2 respectively. Popular Course in this category Data Scientist Training (76 Courses, 60+ Projects)76 Online Courses | 60 Hands-on Projects | 632+ Hours | Verifiable Certificate of Completion | Lifetime Access 4.8 (11,470 ratings) Course Price View Course Related Courses Tableau Training (4 Courses, 6+ Projects)Azure Training (5 Courses, 4 Projects, 4 Quizzes)Hadoop Training Program (20 Courses, 14+ Projects, 4 Quizzes)Data Visualization Training (15 Courses, 5+ Projects)All in One Data Science Bundle (360+ Courses, 50+ projects) tab1: It is the first table name on which a SELECT statement will be applied. tab2: It is the second table name on which a SELECT statement will be applied.	Syntax of using the union all operator in PostgreSQL is:   SELECT exp1, exp2, exp3, . . . from tab1 UNION ALL SELECT exp1, exp2, exp3, . . . from tab2   Where, exp1, exp2, exp3, . . . are the column names that need to be retrieved from tab1 and tab2 respectively. tab1: It is the first table name on which a SELECT statement will be applied. tab2: It is the second table name on which a SELECT statement will be applied.

Conclusion

The above description clearly explains what the PostgreSQL union and union all is and the major differences between the two. Both the UNION and UNION ALL operators are used for the same purpose in PostgreSQL (though the output is different). It depends on the choice of the programmer, data present in the tables, and the required output to the user to use any of them according to their requirements.

Recommended Articles

This is a guide to PostgreSQL union vs union all. Here we discuss PostgreSQL union vs union all key differences with infographics and a comparison table. You may also have a look at the following articles to learn more –

1. OData vs GraphQL
2. Zendesk vs Freshdesk
3. Aerospike vs Redis
4. Program vs Process