Preamble

PostgreSQL DROP TABLE statement allows you to remove a table from a PostgreSQL database.
The simplest syntax for DROP TABLE in PostgreSQL
DROP TABLE table_name;
The full syntax for the PostgreSQL DROP TABLE statement
DROP [ TEMPORARY ] TABLE [ IF EXISTS ]
table_name1, table_name2,...
[ RESTRICT | CASCADE ];
Parameters and arguments of the operator
- TEMPORARY – Optional. It specifies that the DROP TABLE operator should delete only temporary tables.
- table_name – The name of the table to be deleted from the database.
- Table_name1, table_name2 – The tables to be deleted from the database if more than one table in the DROP TABLE operator is deleted.
- IF EXISTS – Optional. If specified, the DROP TABLE statement shall not cause an error if one of the tables does not exist.
- RESTRICT – Optional. If specified, the table will be deleted only if there are no other objects that depend on it.
- CASCADE – Optional. If specified, the table will be deleted and all objects that depend on it will be automatically deleted.
If you use the DROP TABLE operator in PostgreSQL to delete one or more non-existent tables, the database will generate an error (unless you specify the IF EXISTS parameter in the DROP TABLE operator).
Consider an example that shows how to remove a table using the PostgreSQL DROP TABLE operator.
Deleting a single table
First let’s look at a simple DROP TABLE example, which shows how to use DROP TABLE to delete a single table in PostgreSQL.
For example:
DROP TABLE order_details;
This DROP TABLE example will delete the table named order_details.
Deleting multiple tables
Let’s have a look at an example where we want to delete more than one table using the DROP TABLE operator:
For example:
DROP TABLE order_details, products;
This example will delete two tables, order_details, and products. If we are worried that one of the tables doesn’t exist and we don’t want to get an error, we can change our DROP TABLE operator as follows:
DROP TABLE IF EXISTS order_details, products;
This example will delete order_details and product tables and will not generate an error if one of the tables does not exist.
How to Create and Drop Tables in PostgreSQL
Enteros
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
Accurate Healthcare Cloud Cost Estimation with Enteros: An AIOps-Driven FinOps Approach
- 15 January 2026
- Database Performance Management
Introduction Healthcare organizations are undergoing rapid digital transformation. Electronic health records (EHRs), telemedicine platforms, AI-driven diagnostics, patient engagement portals, population health analytics, and regulatory reporting systems now form the backbone of modern healthcare delivery. At the center of all these innovations lies a complex, data-intensive cloud infrastructure powered by mission-critical databases. While cloud adoption has … Continue reading “Accurate Healthcare Cloud Cost Estimation with Enteros: An AIOps-Driven FinOps Approach”
Why Traditional Banking Database Optimization Falls Short, and How Enteros Fixes It with GenAI
Introduction Modern banking has become a real-time, always-on digital business. From core banking systems and payment processing to mobile apps, fraud detection, risk analytics, and regulatory reporting—every critical banking function depends on database performance. Yet while banking technology stacks have evolved dramatically, database optimization practices have not. Most banks still rely on traditional database tuning … Continue reading “Why Traditional Banking Database Optimization Falls Short, and How Enteros Fixes It with GenAI”
Smarter BFSI Database Operations: How Enteros Applies GenAI to Cloud FinOps and RevOps
- 14 January 2026
- Database Performance Management
Introduction Banks, financial institutions, insurers, and fintech organizations operate in one of the most complex and regulated technology environments in the world. Digital banking platforms, real-time payments, core transaction systems, fraud detection engines, regulatory reporting platforms, and customer engagement channels all depend on highly reliable database operations. As BFSI organizations modernize their technology stacks, database … Continue reading “Smarter BFSI Database Operations: How Enteros Applies GenAI to Cloud FinOps and RevOps”
How Enteros Uses AIOps to Transform Database Performance Management and Cloud FinOps
Introduction As enterprises accelerate cloud adoption, digital transformation has fundamentally reshaped how applications are built, deployed, and scaled. At the center of this transformation lies a critical but often overlooked layer: databases. Every transaction, customer interaction, analytics workflow, and AI model ultimately depends on database performance. Yet for many organizations, database performance management and cloud … Continue reading “How Enteros Uses AIOps to Transform Database Performance Management and Cloud FinOps”