Every table has several system columns that are implicitly defined by the system. Therefore, these names cannot be used as names of user-defined columns

PostgreSQL implements table inheritance, which can be a useful tool for database designers. (SQL:1999 and later define a type inheritance feature

When you create a table and you realize that you made a mistake, or the requirements of the application change, you can drop the table and create it again. But this is not

A column can be assigned a default value. When a new row is created and no values are specified for some of the columns, those columns will be filled with their respective

Data types are a way to limit the kind of data that can be stored in a table. For many applications, however, the constraint they provide is too coarse. For example, a column

A table in a relational database is much like a table on paper: It consists of rows and columns. The number and order of the columns is fixed, and each column has a name. The

A PostgreSQL database cluster contains one or more named databases. Users and groups of users are shared across the entire cluster, but no

PostgreSQL supports basic table partitioning. This section describes why and how to implement partitioning as part of your database design

When you create complex database structures involving many tables with foreign key constraints, views, triggers, functions, etc. you implicitly create a net of dependencies

In addition to the SQL-standard privilege system available through