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 esoteric operations, such as adding index access methods.
Table 3-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", "fields")|
|pg_class||tables, indexes, sequences ("relations")|
|pg_database||databases within this database cluster|
|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_opclass||index access method operator classes|
|pg_proc||functions and procedures|
|pg_rewrite||query rewriter rules|
More detailed documentation of most catalogs follow below. The catalogs that relate to index access methods are explained in the Programmer's Guide.
If you see anything in the documentation that is not correct, does not match your experience with the particular feature or requires further clarification, please use this form to report a documentation issue.