Preamble
PostgreSQL Constraints: You’ll learn how to create, add, and remove unique constraints in PostgreSQL with syntax and examples.
What is a unique constraint in PostgreSQL Constraints?
A unique constraint is a single field or a combination of fields that uniquely define a record. Some fields may contain zero values if the combination of values is unique.
What is the difference between a unique constraint and a primary key?
|
Primary key
|
Unique Constraint
|
|---|---|
|
None of the fields, which are part of the primary key, can contain zero value.
|
Some fields that are part of the uniqueness constraint may contain zero values if the combination of values is unique.
|
Create a unique Constraint use the CREATE TABLE operator
Syntax to create a unique constraint using the CREATE TABLE operator in PostgreSQL:
CREATE TABLE table_name
(
column1 datatype [ NULL | NOT NULL ],
column2 datatype [ NULL | NOT NULL ],
...
CONSTRAINT constraint_name UNIQUE (uc_col1, uc_col2,... uc_col_n)
);
- table_name – The name of the table you want to create.
- column1, column2 – The columns you want to create in the table.
- constraint_name – The name of a unique constraint.
- uc_col1, uc_col2,… uc_col_n – The columns that make up the unique constraint.
Consider an example of how to create a unique limitation in PostgreSQL using the CREATE TABLE statement.
CREATE TABLE order_details
( order_detail_id integer CONSTRAINT order_details_pk PRIMARY KEY,
order_id integer NOT NULL,
order_date date,
size integer,
notes varchar(200),
CONSTRAINT order_unique UNIQUE (order_id)
);
In this example, we created a unique restriction for the order_details table called order_unique. It consists of only one field, order_id.
We can also create a unique constraint with more than one field, as in the example below:
CREATE TABLE order_details
( order_detail_id integer CONSTRAINT order_details_pk PRIMARY KEY,
order_id integer NOT NULL,
order_date date,
size integer,
notes varchar(200),
CONSTRAINT order_date_unique UNIQUE (order_id, order_date)
)
Create a unique Constraint using the ALTER TABLE operator
Syntax to create a unique constraint using ALTER TABLE in PostgreSQL:
ALTER TABLE table_name
ADD CONSTRAINT constraint_name UNIQUE (column1, column2,... column_n);
- table_name – Name of the table to change. This is the table to which you want to add a unique constraint.
- constraint_name – The name of the unique constraint.
- column1, column2,… column_n – The columns that make up the unique constraint.
Let’s consider an example of how to add a unique limitation to an existing table in PostgreSQL using the ALTER TABLE operator.
ALTER TABLE order_details
ADD CONSTRAINT order_unique UNIQUE (order_id);
In this example, we have created a unique restriction for an existing order_details table with the name order_unique. It consists of a field with the name order_id.
We can also create a unique constraint with more than one field, as in the example below:
ALTER TABLE order_details
ADD CONSTRAINT order_date_unique UNIQUE (order_id, order_date);
Delete unique Constraint
Syntax to remove the unique restriction in PostgreSQL:
ALTER TABLE table_name
DROP CONSTRAINT constraint_name;
- table_name – The name of the table to change. This is the table from which you want to remove the unique constraint.
- constraint_name – The name of the unique constraint to be removed.
Let’s consider an example of how to remove a unique limitation from a table in PostgreSQL.
ALTER TABLE order_details
DROP CONSTRAINT order_unique;
In this example, we discard a unique restriction on an order_details table named order_unique.
PostgreSQL: Creating Tables with Constraints | Course
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
Scaling AI Without Overspend: How Enteros Brings Financial Clarity to AI Platforms
- 22 January 2026
- Database Performance Management
Introduction Artificial intelligence is no longer experimental. Across industries, AI platforms now power core business functions—recommendation engines, fraud detection, predictive analytics, conversational interfaces, autonomous decision systems, and generative AI applications. But as AI adoption accelerates, a critical problem is emerging just as fast: AI is expensive—and most organizations don’t fully understand why. Read more”Indian Country” … Continue reading “Scaling AI Without Overspend: How Enteros Brings Financial Clarity to AI Platforms”
AI-Native Database Performance Management for Real Estate Technology Enterprises with Enteros
Introduction Real estate has rapidly evolved into a technology-driven industry. From digital property marketplaces and listing platforms to smart building systems, valuation engines, CRM platforms, and AI-powered analytics, modern real estate enterprises run on data-intensive technology stacks. At the center of this transformation lies a critical foundation: databases. Every property search, pricing update, lease transaction, … Continue reading “AI-Native Database Performance Management for Real Estate Technology Enterprises with Enteros”
Driving RevOps Efficiency Through AI-Driven Database Optimization with Enteros
- 21 January 2026
- Database Performance Management
Introduction Revenue Operations (RevOps) has become the backbone of modern digital enterprises. By aligning sales, marketing, finance, and customer success, RevOps promises predictable growth, faster decision-making, and improved customer lifetime value. Yet, for many organizations, RevOps efficiency remains elusive. The missing link is often hidden deep within the technology stack: the database layer. Every revenue … Continue reading “Driving RevOps Efficiency Through AI-Driven Database Optimization with Enteros”
How Retail Companies Can Reduce Cloud Costs Through Database Optimization with Enteros
Introduction Retail has become one of the most data-intensive industries in the digital economy. Modern retailers rely on cloud-powered platforms to support omnichannel commerce, real-time inventory visibility, personalized recommendations, dynamic pricing, loyalty programs, supply chain optimization, and customer analytics. At the center of all these capabilities sits a critical layer: databases. Retail databases process millions … Continue reading “How Retail Companies Can Reduce Cloud Costs Through Database Optimization with Enteros”