While writing queries in PostgreSQL, there would be some situations where you would be tired of selecting all the records and then filtering them. And also, filtering them would require writing numerous lines of unnecessary and redundant code.
This is where PostgreSQL Subquery comes to your rescue. PostgreSQL Subquery can reduce the lines of your code by multifold and you can easily filter out your data based on any condition you desire.
This article will help you comprehensively understand the overall usage and need of the PostgreSQL Subquery. You will also come across the different kinds of use cases and query examples of PostgreSQL Subquery.
What is a PostgreSQL Subquery?
A PostgreSQL Subquery is basically a query nested inside a larger query.
The rules and guidelines that should be kept in mind while using PostgreSQL Subqueries are as follows:
- PostgreSQL Subqueries should be enclosed within parentheses.
- If you’re using a PostgreSQL Subquery with the SELECT clause, then you can have only one column along with it unless multiple columns are in the main query for the subquery to compare its selected columns.
- An ORDER BY clause cannot be used in a PostgreSQL Subquery, although the main query can use an ORDER BY. The GROUP BY can be used to perform the same function as the ORDER BY in a subquery.
- PostgreSQL Subqueries that return more than one row can only be used with multiple value operators, such as the IN, EXISTS, ALL, NOT IN, ANY, SOME, etc.
- The BETWEEN operator cannot be used with a subquery. Rather, it can be used within the subquery.
- You can only use single-row operators with single-row PostgreSQL Subqueries, and multiple-row operators with multiple-row PostgreSQL Subqueries.
- When using certain comparison operators in a WHERE clause, if a subquery (inner query) returns a null value to the parent query (outer query), then the outer query won’t return any rows.
Unlock the power of your PostgreSQL data by seamlessly connecting it to various destinations, enabling comprehensive analysis in tools like Google Data Studio.
Check out Why Hevo is the right choice for you!
- No-Code Platform: Easily set up and manage your data pipelines without any coding.
- Auto-Schema Mapping: Automatically map schemas for smooth data transfer.
- Pre and Post-Load Transformations: Transform your data at any stage of the migration process.
- Real-Time Data Ingestion: Keep your data up-to-date with real-time synchronization.
Join over 2000 happy customers who trust Hevo for their data integration needs and experience why we are rated 4.7 on Capterra.
Get Started with Hevo for Free
PostgreSQL Subquery: Overview
PostgreSQL Subquery can accommodate a variety of use cases. These are as follows:
I) With different Statements
You can use a PostgreSQL Subquery along with different statements based on whether you want to query, insert, update or delete data from your table(s).
The statements along which you can use PostgreSQL Subquery are as follows:
1) SELECT statement
While retrieving information if you want to restrict your data set then you can fulfill this by creating a PostgreSQL Subquery inside the main query.
A) Syntax
SELECT column_name [, column_name ]
FROM table1 [, table2 ]
WHERE column_name OPERATOR
(SELECT column_name [, column_name ]
FROM table1 [, table2 ]
[WHERE])
In this case, the query written inside parentheses is the Subquery or the nested query.
B) Example
SELECT * FROM EMPLOYEE
WHERE ID IN (SELECT ID
FROM EMPLOYEE
WHERE SALARY > 50000);
This query will display all the information about the employees from the Employee table whose salary would be greater than 50,000.
The output would be similar to
2) INSERT statement
You can create a PostgreSQL Subquery to help you insert data in a table (or view) on the basis of the data returned by the subquery. You can also modify the data queried by the subquery by using any of the character, date, or number functions.
A) Syntax
INSERT INTO table_name [ (column_1 [, column_2 ]) ]
SELECT [ *|col_1 [, col_2 ] ]
FROM table_1 [, table_2 ]
[ WHERE VALUE OPERATOR ]
In this case, you are inserting values inside the table_name table on the basis of the data retrieved by using a PostgreSQL Subquery.
B) Example
INSERT INTO EMPLOYEE_HANDBOOK
SELECT * FROM EMPLOYEE
WHERE ID IN (SELECT ID
FROM EMPLOYEE);
This query will insert all the information about the employees into the EMPLOYEE_HANDBOOK table from the EMPLOYEE table on the basis of their ID.
3) UPDATE statement
You can update one or more columns in a table on the basis of data returned by a PostgreSQL Subquery.
A) Syntax
UPDATE table_n1
SET col_name = new_value
[ WHERE OPERATOR [ VALUE ]
(SELECT COL_NAME
FROM TAB_NAME)
[ WHERE) ]
In this case, you are updating the values of the records in the column col_name of the tab_n1 table on the basis of some condition written in the PostgreSQL Subquery.
2) Example
UPDATE ORG
SET SALARY = SALARY * 0.75
WHERE AGE IN (SELECT AGE FROM EMPLOYEE
WHERE AGE >= 29 );
This query will update the salary of the employees in the ORG table by 3/4th on the basis of whose age is greater than or equal to 29 from the EMPLOYEE table.
4) DELETE statement
You can delete one or more columns in a table on the basis of data returned by a PostgreSQL Subquery.
A) Syntax
DELETE FROM TAB_NAME
[ WHERE OPERATOR [ VALUE ]
(SELECT COL_NAME
FROM TABLE_NAME)
[ WHERE) ]
In this case, you are deleting all the records in the TAB_NAME table on the basis of some condition written in the PostgreSQL Subquery.
B) Example
DELETE FROM EMPLOYEE_HANDBOOK
WHERE AGE IN (SELECT AGE FROM EMPLOYEE
WHERE AGE > 27 );
This query will delete all the records in the EMPLOYEE_HANDBOOK table whose age is greater than 27.
Connect Postgres as your Source or Destination Within Minutes!
No credit card required
II) With different Clauses
You can use a PostgreSQL Subquery along with different statements based on whether you want to query, insert, update or delete data from your table(s).
The clause along which you can use PostgreSQL Subquery is as follows:
1) SELECT clause
While performing any CRUD operation in PostgreSQL, you can use a PostgreSQL Subquery in a SELECT statement.
A) Syntax
The overall syntax would be:
SELECT…., (SELECT...) FROM table_name…;
B) Example
To have a detailed idea, you can follow the given query:
SELECT b1.bike_name, b1.bike_model,
(SELECT MIN (bike_id)
FROM bike b2
WHERE b1.bike_id = b2.bike_id) //Subquery
FROM bike b1;
The query written inside the parentheses is the PostgreSQL Subquery which is used along with the SELECT clause to find the minimum bike id. The MIN() is an aggregate function that is used in the Subquery to filter out the records.
2) FROM clause
While writing queries in PostgreSQL, you can use a PostgreSQL Subquery in a SELECT statement’s FROM clause.
A) Syntax
The overall syntax would be:
SELECT...FROM (Subquery) [AS] name…;
Since every table in a FROM clause must have a name, the [AS] name clause is required. Column names in the subquery select list must be unique.
B) Example
To have a detailed idea, you can follow the given query:
select A.id, A.name, A.dept, A.salary FROM
(select avg(budget) as avg_budget from DEPARTMENT) as TARGET T, INSTRUCTOR as A
where A.salary > T.avg_budget;
The query written inside the parentheses is the PostgreSQL Subquery which is treated as a virtual table and the data it returns is fed to a buffer table called TARGET.
3) WHERE clause
While performing any CRUD operation in PostgreSQL, you can use a PostgreSQL Subquery along with a SELECT clause.
A) Syntax
The overall syntax would be:
SELECT … FROM table_name WHERE col_name IN (Subquery);
Here, Subquery is a selected range used in the WHERE clause for setting a specific condition.
B) Example
To have a detailed idea, you can follow the given query:
SELECT p.prod_id, p.prod_name
FROM product p
WHERE p.cat_id IN
(SELECT c.cat_id
FROM category c
WHERE c.cat_id > 30
AND c.cat_name like 'M%');
The query written inside the parentheses is the PostgreSQL Subquery which is used along with the WHERE IN clause to set the condition for retrieving the records.
Also, take a look at how you can easily work with PostgreSQL UNION & UNION ALL operators.
III) With different Conditions
You can use a PostgreSQL Subquery along with different condition statements.
The different conditions used with PostgreSQL Subquery are as follows:
1) EXISTS condition
You can use a PostgreSQL Subquery along with the EXISTS clause. The EXISTS clause only keeps the number of rows returned by the subquery.
A) Syntax
The basic syntax is as follows:
……
EXISTS
(SELECT col_name, [column_name|expressions]
FROM table_name
WHERE condition);
The PostgreSQL Subquery is an input of the EXISTS condition. The EXISTS condition will return TRUE if the Subquery returns any row. And if the subquery returns no results, the EXISTS condition will return FALSE.
B) Example
SELECT *
FROM customer
WHERE EXISTS
(SELECT *
FROM order
WHERE customer.cus_id = order.cus_id);
This query will return all the information of those customers who have made any orders.
2) IN condition
You can use a PostgreSQL Subquery along with the IN condition. In this case, you are creating the subquery with a WHERE clause and IN condition.
A) Syntax
The basic syntax is as follows:
Here, the PostgreSQL Subquery is used to set a specific condition by using it with the WHERE clause and IN condition.
B) Example
SELECT emp_name
FROM Employee
WHERE Department IN
(SELECT dept_no
FROM Department
WHERE floor = 5);
This query will return all the names of the employees whose departments are on the 5th floor.
Integrate PostgreSQL to MySQL
Integrate PostgreSQL to Snowflake
Integrate PostgreSQL on Amazon RDS to Databricks
IV) For doing Comparisons
You can use a PostgreSQL Subquery before or after any of the comparison operators. The subquery will return at most one value. The value will be the result of an arithmetic expression or a column function. Your query then compares the subquery result to the value on the other side of the comparison operator.
The different comparison operators that can be used are as follows:
Example
SELECT emp_id,f_name,l_name,salary
FROM Employee
WHERE salary >
(SELECT AVG(salary) FROM Employee);
In this example, the records are displayed on the basis of comparing the salary of all the employees.
You can also checkout how you can effortlessly work with the PostgreSQL Now() Function.
V) PostgreSQL Subquery with ALL, ANY, and SOME Operators
You can use PostgreSQL Subquery with ALL, ANY, and SOME Operators.
1) ALL Operator
When the ALL operator is used along with a PostgreSQL Subquery, it will help you compare the value in the main query to every value returned by the subquery.
A) Syntax
The basic syntax is as follows:
The parenthesized subquery on the right will return exactly one column. Using the given operator, the left-hand expression is evaluated and compared to each row of the subquery result, which must return a Boolean result.
- The subquery will return true if all rows return true (including the case where the subquery returns no rows).
- If any false results are detected, the result will be false.
- If the comparison does not return false for any row and returns NULL for at least one row, the result is NULL.
B) Example
SELECT dept_id, AVG(salary)
FROM EMPLOYEE GROUP BY dept_id
HAVING AVG(salary)>=ALL
(SELECT AVG(Salary) FROM EMPLOYEE
GROUP BY dept_id);
In this query, ALL will help with comparing all the average salaries of all the employees department-wise.
2) ANY/SOME Operator
The ANY operator compares the value to each of the subquery’s results. As a result, the ANY keyword returns TRUE if the comparison is TRUE for ANY of the values in the column returned by the subquery. And SOME Operator is synonymous with the ANY operator.
A) Syntax
The basic syntax is as follows:
expression operator SOME (subquery);
B) Example
SELECT first_name, last_name,department_id
FROM employees
WHERE department_id= ANY
(SELECT DEPARTMENT_ID
FROM departments WHERE location_id=1700);
In this query, ANY will help with comparing the average salaries of all the employees department-wise. The result of the query will be based on comparing with any of the values returned by the PostgreSQL Subquery.
For further information on PostgreSQL Documentation, you can visit the official website.
Why do you use PostgreSQL Subqueries?
A PostgreSQL Subquery is used to return data that will be utilized as a condition in the main query to further limit the data to be returned. You may also use it when the desired result demands more than one query and each subquery returns a subset of the table involved in the query.
Also, explore your PostgreSQL knowledge by understanding how PostgreSQL Stored Procedures work.
Conclusion
This article illustrated the concept of PostgreSQL Subquery. You had an in-depth understanding of why there is a need to create a PostgreSQL Subquery, its different use cases, and all the parameters in it.
Now, you can move forward and write your Subqueries in PostgreSQL according to your use cases.
If you use PostgreSQL, ingesting and moving data into your selected warehouse using ETL for Data Analysis might be a time-consuming process. When you realize how much money and resources are required to engage data engineers and analysts to make sense of this data, the situation becomes even more daunting.
However, with Hevo at your fingertips, you won’t have to worry about your PostgreSQL Data Replication demands. Loading your data into your selected data warehouse will only take a few minutes.
Sign up for a 14-day free trial and simplify your data integration process. Check out the pricing details to understand which plan fulfills all your business needs.
Frequently Asked Questions
1. What is a subquery in PostgreSQL?
A subquery is a query nested inside another query. It is used to perform operations like filtering or computing values that are used in the main query.
2. How can I use a subquery in a SELECT statement?
You can use a subquery in a SELECT statement to fetch data from a related table. The result from the subquery is used in the main query to filter or compute values.
3. What’s the difference between EXISTS and IN in PostgreSQL subqueries?
EXISTS checks if any rows are returned by the subquery, while IN checks if a value matches any values returned by the subquery. EXISTS is often more efficient in some cases.
Manisha Jena is a data analyst with over three years of experience in the data industry and is well-versed with advanced data tools such as Snowflake, Looker Studio, and Google BigQuery. She is an alumna of NIT Rourkela and excels in extracting critical insights from complex databases and enhancing data visualization through comprehensive dashboards. Manisha has authored over a hundred articles on diverse topics related to data engineering, and loves breaking down complex topics to help data practitioners solve their doubts related to data engineering.