Preamble
PostgreSQL UNION statement is used to combine the resulting sets of 2 or more SELECT operators. It removes repetitive lines between different SELECT operators.
Each SELECT statement in a UNION operator must have the same number of fields in the result sets with the same data types.
The syntax for a UNION statement in PostgreSQL
SELECT expression1_id, expression2_id,... expression_n_id
FROM tabs
[WHERE conds]
UNION
SELECT expression1_id, expression2_id,... expression_n_id
FROM tabs
[WHERE conds];
Parameters and arguments of the statement
- expression1_id, expression2_id,…_n_id – The column or the calculation you want to get.
- tabs – The tables from which you want to get the records. The FROM operator must specify at least one table.
- WHERE conds – Optional. The conditions to be met for the records to be selected.
Note:
- Both SELECT statements must have the same number of expressions.
- Since the UNION operator by default removes all repetitive strings from the result set, providing a UNION DISTINCT modifier does not affect the results.
- The column names from the first SELECT operator in UNION are used as column names for the result set.
Example with the return of a single field
Below is an example of PostgreSQL UNION operator, which returns one field from several SELECT operators (and both fields have the same data type):
SELECT category_id
FROM products
UNION
SELECT category_id
FROM categories;
In this example of the PostgreSQL UNION operator, if a category_id appears in both the products table and the categories table, it will appear in your resulting set once. The PostgreSQL UNION statement removes duplicates. If you do not want to remove duplicates, try using PostgreSQL UNION ALL operator.
Example using the ORDER BY statement
PostgreSQL UNION operator can use ORDER BY operator to organize query results.
For example:
SELECT product_id, product_name
FROM products
WHERE product_id >= 24
UNION
SELECT category_id, category_name
FROM categories
WHERE category_name <> 'Hardware'
ORDER BY 2;
In this PostgreSQL operator UNION, since column names in two SELECT operators are different, it is more advantageous to refer to columns in ORDER BY operator by their position in the resulting set. In this example, we have sorted the results by product_name / category_name in ascending order as ORDER BY 2.
The product_name / category_name fields are at position #2 in the resulting set. is used to combine the resulting sets of 2 or more SELECT operators. It removes repetitive lines between different SELECT operators.
Each SELECT statement in a UNION operator must have the same number of fields in the result sets with the same data types.
PostgreSQL Tutorial – UNION and UNION ALL
About Enteros
Enteros offers a patented database performance management SaaS platform. It proactively identifies root causes of complex business-impacting database scalability and performance issues across a growing number of clouds, RDBMS, NoSQL, and machine learning database platforms.
The views expressed on this blog are those of the author and do not necessarily reflect the opinions of Enteros Inc. This blog may contain links to the content of third-party sites. By providing such links, Enteros Inc. does not adopt, guarantee, approve, or endorse the information, views, or products available on such sites.
Are you interested in writing for Enteros’ Blog? Please send us a pitch!
RELATED POSTS
Smarter Retail IT: How Enteros Enhances Performance Management and Cost Attribution for SaaS Database Ecosystems
- 9 December 2025
- Database Performance Management
Introduction The retail industry is undergoing one of the most significant digital shifts in modern history. From omnichannel commerce and real-time inventory visibility to personalized customer experiences powered by AI and data analytics, retailers rely heavily on SaaS-based platforms and high-performance databases to keep their digital operations running seamlessly. Yet, this digital acceleration brings new … Continue reading “Smarter Retail IT: How Enteros Enhances Performance Management and Cost Attribution for SaaS Database Ecosystems”
Unlocking Financial Performance: How Enteros Elevates Database Optimization with Intelligent Cost Attribution
Introduction The financial sector operates in a landscape where precision, performance, and transparency are non-negotiable. Banks, investment firms, payment providers, and fintech enterprises depend on massive data ecosystems to power transactions, risk models, compliance reporting, customer analytics, and digital-first experiences. As these data workloads scale across hybrid and multi-cloud environments, ensuring optimal database performance and … Continue reading “Unlocking Financial Performance: How Enteros Elevates Database Optimization with Intelligent Cost Attribution”
The Future of Financial RevOps: Enteros’ AIOps-Powered Framework for Precision Cost Estimation
- 8 December 2025
- Database Performance Management
Introduction The financial sector is undergoing a massive transformation driven by digital acceleration, regulatory pressure, cloud migration, AI adoption, and rising customer expectations. Banks, insurance companies, fintechs, and wealth management firms now operate in a hyper-competitive landscape where agility, accuracy, and operational efficiency determine long-term success. Within this environment, Revenue Operations (RevOps) has emerged as … Continue reading “The Future of Financial RevOps: Enteros’ AIOps-Powered Framework for Precision Cost Estimation”
What Technology Teams Gain from Enteros’ GenAI-Driven Database Performance and Cloud FinOps Intelligence
Introduction The technology sector is entering a new era—one where rapid innovation, distributed architectures, and cloud-native systems fuel unprecedented digital acceleration. Yet behind this momentum sits a challenge that every CTO, DevOps leader, and cloud architect knows all too well: how do you maintain high performance, manage cost efficiency, and ensure seamless database reliability across … Continue reading “What Technology Teams Gain from Enteros’ GenAI-Driven Database Performance and Cloud FinOps Intelligence”