Preamble
PostgreSQL BETWEEN condition is used to obtain values in the range in SELECT, INSERT, UPDATE, or DELETE operator.
The syntax for BETWEEN condition in PostgreSQL
expression BETWEEN value1_id AND value2_id;
Parameters and arguments of the condition
- expression – Column or calculation.
- value1_id and value2_id – These values create an inclusive range with which the expression is compared.
Note:
- PostgreSQL condition BETWEEN will return records where expression is in the value1 and value2 ranges (inclusive).
Example BETWEEN condition with numbers
Consider some examples of PostgreSQL BETWEEN conditions using numeric values. In the following example, the BETWEEN condition is used to obtain values within a numeric range.
For example:
SELECT *
FROM empls
WHERE empl_id BETWEEN 500 AND 600;
In this example, all rows from the employee_id table will be returned, where employee_id is between 500 and 600 (inclusive). This is equivalent to the next SELECT operator :
SELECT *
FROM empls
WHERE empl_id >= 500
AND empl_id <= 600;
Example BETWEEN condition with dates
Now let’s see how you will use the PostgreSQL condition BETWEEN with dates.
In the following example, the BETWEEN condition is used to obtain values within a date range.
For example:
SELECT *
FROM empls
WHERE start_date BETWEEN '2019-04-01' AND '2019-04-30';
In this example, the BETWEEN condition will return all entries from the table where start_date is from April 1, 2019 to April 30, 2019 (inclusive). This would be equivalent to the next SELECT query:
SELECT *
FROM empls
WHERE start_date >= '01.04.2019'
AND start_date <= '30.04.2019';
Example of a condition using the NOT operator
PostgreSQL condition BETWEEN can also be combined with NOT operator. Here is an example of how you could combine a BETWEEN condition with the NOT operator.
For example:
SELECT *
FROM empls
WHERE empl_id NOT BETWEEN 700 AND 799;
This PostgreSQL example BETWEEN would return all rows from the employee table where employee_id is not between 700 and 799 inclusive. This would be equivalent to the next SELECT operator:
SELECT *
FROM empls
WHERE empl_id < 700
OR empl_id > 799;
PostgreSQL Tutorial for Beginners PostgreSQL BETWEEN 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 Resilience During Peak Transaction Volumes?
- 10 September 2026
- Database Performance Management
Banks can improve banking database resilience by continuously monitoring transaction workloads, optimizing SQL, detecting abnormal behavior, reducing locking and resource contention, analyzing peak-demand patterns and forecasting capacity requirements. Database observability helps teams identify performance risks before customers experience failures. Enteros combines workload intelligence, anomaly detection, predictive analytics and root cause analysis to support resilient banking … Continue reading “How Can Banks Improve Database Resilience During Peak Transaction Volumes?”
How Can Healthcare IT Teams Prepare EHR Databases for Growth and Peak Demand?
Healthcare IT teams can prepare EHR databases for growth by monitoring workload trends, forecasting CPU, memory and storage requirements, optimizing high-impact SQL, analyzing concurrency, establishing performance baselines and testing future workloads. Healthcare database capacity planning helps organizations identify resource constraints before they disrupt clinical systems. Enteros provides database observability and predictive intelligence to support proactive … Continue reading “How Can Healthcare IT Teams Prepare EHR Databases for Growth and Peak Demand?”
What Is the Best Way for Telecom Companies to Monitor Database Performance in Real Time?
- 9 September 2026
- Database Performance Management
The best approach to telecom database performance monitoring is continuous, real-time observability across databases, applications, infrastructure, and workloads. Telecom companies should track query latency, resource utilization, waits, connections, anomalies, and configuration changes from a centralized platform. Intelligent telecom database monitoring helps teams identify performance degradation earlier, accelerate root cause analysis, reduce service disruptions, and maintain … Continue reading “What Is the Best Way for Telecom Companies to Monitor Database Performance in Real Time?”
Why Does Database Performance Matter for Faster E-commerce and In-Store Transactions?
Strong ecommerce database performance helps retailers process online and in-store transactions quickly, maintain accurate inventory, and deliver responsive customer experiences. When databases operate efficiently, product searches, checkout requests, payment workflows, and stock updates can complete with fewer delays. Effective database performance for ecommerce also helps businesses handle traffic spikes, identify bottlenecks, maintain availability, and support … Continue reading “Why Does Database Performance Matter for Faster E-commerce and In-Store Transactions?”