Skip to main content

​
Overview

The PostgreSQL Virtual Catalog tables represent Kinetica’s implementation of the PostgreSQL system catalog tables found in the pg_catalog schema. These These tables contain information about the database’s objects, relationships, & permissions. Most of the metadata tables are implemented as logical views of the Kinetica Virtual Catalog tables, while some are logical views of other PostgreSQL Virtual Catalog logical views. As such, they will be updated automatically to reflect changes in the database structure and processing state. The information returned when querying the virtual catalogs is automatically filtered by the permissions of the querying user. For instance, regular users will only see the tables & views to which they have access when querying a virtual catalog table that lists all of the tables in the database, while system administrators will see all tables & views.

​
Catalog View List

The PostgreSQL Virtual Catalog tables reside in the pg_catalog schema.
Kinetica implements the pg_catalog relations above. Other relations from the PostgreSQL system catalog are present, so that clients probing for them succeed, but they return no records.

​
Primary Key Indexes

Kinetica follows the PostgreSQL convention of exposing each primary key as an index, rather than as a relation of its own. Each appears as a record in pg_class, with a relname of <table_name>\ _pkey and a relkind of i, and as a corresponding record in pg_index. For example, the primary key on ki_catalog.ki_datatypes is reported as ki_datatypes_pkey. These are index records; they have no columns of their own and will not appear in ki_columns or in any listing of catalog tables.