The system catalogs are the place where a relational database management system stores schema metadata, such as information about tables and columns, and internal bookkeeping information. PostgreSQL's system catalogs are regular tables. You can drop and recreate the tables, add columns, insert and update values, and severely mess up your system that way. Normally, one should not change the system catalogs by hand, there are always SQL commands to do that. (For example, CREATE DATABASE inserts a row into the pg_database catalog --- and actually creates the database on disk.) There are some exceptions for particularly esoteric operations, such as adding index access methods.
Table 43-1 lists the system catalogs. More detailed documentation of each catalog follows below.
Most system catalogs are copied from the template database during database creation and are thereafter database-specific. A few catalogs are physically shared across all databases in a cluster; these are marked in the descriptions of the individual catalogs.
Table 43-1. System Catalogs
|pg_am||index access methods|
|pg_amop||access method operators|
|pg_amproc||access method support procedures|
|pg_attrdef||column default values|
|pg_attribute||table columns ("attributes")|
|pg_cast||casts (data type conversions)|
|pg_class||tables, indexes, sequences ("relations")|
|pg_constraint||check constraints, unique constraints, primary key constraints, foreign key constraints|
|pg_conversion||encoding conversion information|
|pg_database||databases within this database cluster|
|pg_depend||dependencies between database objects|
|pg_description||descriptions or comments on database objects|
|pg_group||groups of database users|
|pg_index||additional index information|
|pg_inherits||table inheritance hierarchy|
|pg_language||languages for writing functions|
|pg_listener||asynchronous notification support|
|pg_opclass||index access method operator classes|
|pg_proc||functions and procedures|
|pg_rewrite||query rewrite rules|