Preamble
PostgreSQL EXISTS condition is used in combination with a subquery and is considered “satisfied” if the subquery returns at least one line. It can be used in SELECT, INSERT, UPDATE, or DELETE statements.
The syntax for PostgreSQL EXISTS condition
WHERE EXISTS ( subquery );
Parameters and arguments of the condition
- subquery – A SELECT operator which usually starts with SELECT *, not with a list of expressions or column names. To improve performance, you can replace SELECT * with SELECT 1 because the result of the subquery column does not matter (only the returned rows are important).
Note:
- SQL statements that use the EXISTS condition in PostgreSQL are very inefficient because the subquery is restarted for EVERY line in the external query table. There are more efficient ways to write most queries that do not use the EXISTS condition.
Example EXISTS Condition with SELECT Operator
Let us consider a simple example. Below is the SELECT operator which uses PostgreSQL condition EXISTS:
SELECT *
FROM products
WHERE EXISTS (SELECT 1
FROM inventory
WHERE products.product_id = inventory.product_id);
In this PostgreSQL EXISTS condition example, it will return all entries from the products table where the inventory table has at least one entry with the matching product_id. We used SELECT 1 in the subquery to improve performance because the resulting set of columns has nothing to do with the EXISTS condition (only the returned row counts).
Example of a SELECT operator using NOT EXISTS
PostgreSQL condition EXISTS can also be combined with NOT operator.
For example,
SELECT *
FROM products
WHERE DOES NOT EXIST (SELECT 1
FROM inventory
WHERE products.product_id = inventory.product_id);
In this PostgreSQL example EXISTS will return all records from the Products table, where the inventory table has no records for this product_id).
Example EXISTS condition with INSERT operator
Below is an example of the INSERT operator which uses PostgreSQL condition EXISTS:
INSERT INTO contacts
(contact_id, contact_name)
SELECT supplier_id, supplier_name
FROM suppliers
WHERE EXISTS (SELECT 1
FROM orders
WHERE suppliers.supplier_id = orders.supplier_id);
Example of condition with UPDATE operator
Below is an example of UPDATE operator, which uses PostgreSQL condition EXISTS:
UPDATE suppliers
SET supplier_name = (SELECT customers.customer_name
FROM customers
WHERE customers.customer_id = suppliers.supplier_id)
WHERE EXISTS (SELECT 1
FROM customers
WHERE customers.customer_id = supplier_id);
Example of PostgreSQL EXISTS condition with DELETE operator
Below is an example of a DELETE operator that uses PostgreSQL EXISTS condition:
DELETE FROM contacts
WHERE EXISTS (SELECT 1
FROM employees
WHERE contacts.contact_id = employees.employee_id);
PostgreSQL EXISTS condition
About Enteros
IT organizations routinely spend days and weeks troubleshooting production database performance issues across multitudes of critical business systems. Fast and reliable resolution of database performance problems by Enteros enables businesses to generate and save millions of direct revenue, minimize waste of employees’ productivity, reduce the number of licenses, servers, and cloud resources and maximize the productivity of the application, database, and IT operations teams.
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
How Can Banks Improve Database Performance for Real-Time Payment Processing?
- 7 September 2026
- Database Performance Management
Strong bank database performance is essential for real-time payment processing because every payment depends on databases retrieving, validating, updating, and recording financial information with minimal delay. Banks can improve bank database performance by optimizing high-impact SQL queries, reducing locking and resource contention, monitoring transaction latency, establishing workload baselines, planning capacity, and using database observability to … Continue reading “How Can Banks Improve Database Performance for Real-Time Payment Processing?”
How Can Database Observability Help Banks Prevent Transaction Failures and Downtime?
With database observability, banks can identify performance anomalies, see how databases are performing, find bottlenecks, and troubleshoot the root causes of transaction failures before they turn into major service outages. Database observability provides banking IT teams with increased visibility into queries, workloads, resource consumption, waits, blocking and performance patterns as they evolve. This proactive visibility … Continue reading “How Can Database Observability Help Banks Prevent Transaction Failures and Downtime?”
How Can Database Observability Help Retail Companies Resolve Performance Issues Faster?
Database observability for retail helps retailers detect, understand, and resolve performance problems faster by providing deep visibility into database workloads, queries, waits, anomalies, and dependencies. Instead of reacting only after applications slow down, retail IT teams can identify root causes earlier, reduce troubleshooting time, improve uptime, and strengthen database performance monitoring for retail across stores, … Continue reading “How Can Database Observability Help Retail Companies Resolve Performance Issues Faster?”
How Can Database Observability Help Telecom Companies Resolve Performance Issues Faster?
Database observability for telecom helps telecom companies detect, investigate, and resolve database performance problems faster by providing deeper visibility into queries, workloads, waits, dependencies, and anomalies. Instead of relying only on basic infrastructure metrics, teams can identify root causes sooner, reduce troubleshooting time, improve service reliability, and support stronger telecom database performance across complex, high-volume … Continue reading “How Can Database Observability Help Telecom Companies Resolve Performance Issues Faster?”