Drop Down MenusCSS Drop Down MenuPure CSS Dropdown Menu

PostgreSQL System Catalog Views

  • Catalogs are named collections of schemas in an SQL-environment
  • When you create a table, PostgreSQL stores the definition of that table in the system catalog. The system catalog is a collection of PostgreSQL tables. You can issue SELECT statements against the system catalog tables just like any other table, but there are easier ways to view table and index definitions.
  • A cluster is an implementation-defined collection of catalogs.
  • Exactly one cluster is associated with an SQL-session
Different between catalog and schema:
Cluster > Catalog > Schema > Table > Columns & Rows
So in both Postgres and the SQL Standard we have this containment hierarchy:

  • A computer may have one cluster or multiple.
  • A database server is a cluster.
  • A cluster has catalogs. ( Catalog = Database )
  • Catalogs have schemas. (Schema = namespace of tables, and security boundary)
  • Schemas have tables.
  • Tables have rows.
  • Rows have values, defined by columns.
When you are using the psql client application, you can view the list of tables defined in your database using the \d meta-command ,\dS+ means more info: 
postgres=# \d
                List of relations
 Schema |       Name        |   Type   |  Owner   
--------+-------------------+----------+----------
 public | batch             | table    | postgres
 public | cellphones        | table    | postgres
 public | cellphones_id_seq | sequence | postgres
 public | distributorc      | table    | u8
postgres=# \dS+
                                       List of relations
   Schema   |              Name               |   Type   |  Owner   |    Size    | Description 
------------+---------------------------------+----------+----------+------------+-------------
 pg_catalog | pg_views                        | view     | postgres | 0 bytes    | 
 public     | batch                           | table    | postgres | 8192 bytes | 
 public     | cellphones                      | table    | postgres | 0 bytes    | 
 public     | cellphones_id_seq               | sequence | postgres | 8192 bytes | 
 public     | distributorc                    | table    | u8       | 0 bytes    | 
 public     | distributors                    | table    | u8       | 0 bytes    | 
 public     | distributorsct                  | table    | u8       | 0 bytes    | 







To see the detailed definition of a particular table, use the \d table-name meta-command:


postgres=# \d batch
          Table "public.batch"
   Column   |     Type      | Modifiers 
------------+---------------+-----------
 batch_id   | integer       | 
 batch_name | character(35) | 
 members    | integer       | 
Indexes:
    "mul_uni_key" UNIQUE CONSTRAINT, btree (batch_id, members)





You can also view a list of all indexes defined in your database. The \di meta-command displays indexes:


postgres=# \di
                         List of relations
 Schema |          Name           | Type  |  Owner   |    Table     
--------+-------------------------+-------+----------+--------------
 public | cellphones_pkey         | index | postgres | cellphones
 public | code_title              | index | u8       | primtab
 public | distributors_pkey       | index | u8       | distributors
 public | mobiles_pkey            | index | postgres | mobiles
 public | mul_uni_key             | index | postgres | batch


postgres=# \diS+
                                                      List of relations
   Schema   |                  Name                   | Type  |  Owner   |          Table          |    Size    | Description 
------------+-----------------------------------------+-------+----------+-------------------------+------------+-------------
 pg_catalog | pg_user_mapping_user_server_index       | index | postgres | pg_user_mapping         | 8192 bytes | 
 .
 .
 .
 public     | cellphones_pkey                         | index | postgres | cellphones              | 8192 bytes | 
 public     | code_title                              | index | u8       | primtab                 | 8192 bytes | 
 public     | distributors_pkey                       | index | u8       | distributors            | 8192 bytes | 
 public     | mobiles_pkey                            | index | postgres | mobiles                 | 16 kB      | 
 public     | mul_uni_key                             | index | postgres | batch                   | 16 kB      | 
 public     | pkey                                    | index | postgres | postgres3               | 16 kB      | 
 public     | postgres1_order_no_key                  | index | postgres | postgres1               | 16 kB      | 
 public     | postgres_ord_no_key                     | index | postgres | postgres                | 8192 bytes | 
 public     | prikey                                  | index | u8       | films                   | 8192 bytes | 
 public     | production                              | index | u8       | k                       | 8192 bytes | 
 public     | students_student_id_key                 | index | postgres | students                | 16 kB      | 
 public     | uni_constraint                          | index | postgres | cellphones              | 8192 bytes | 
 public     | uni_constraint2                         | index | postgres | mobiles                 | 16 kB      | 
 public     | uni_index                               | index | postgres | cellphones              | 8192 bytes | 
 public     | uni_key                                 | index | postgres | india                   | 8192 bytes | 
(110 rows)



You can see the full definition for any given index using the \d index-name meta-command:


postgres=# \diS+ uni_key
                           List of relations
 Schema |  Name   | Type  |  Owner   | Table |    Size    | Description 
--------+---------+-------+----------+-------+------------+-------------
 public | uni_key | index | postgres | india | 8192 bytes | 
(1 row)



System Catalog Meta-Commands




 

   

Command

   

Result

  

 

  

\dd object-name

  

Display comments for object-name

 


  

\db

  

List all tablespaces

 


  

\dn

  

List all schemas

 


  

\d_\dt

  

List all tables

 


  

\di

  

List all indexes

 


  

\ds

  

List all sequences

 


  

\dv

  

List all views

 


  

\dS

  

List all   PostgreSQL-defined tables

 


  

\d table-name

  

Show table definition

 


  

\d index-name

  

Show index definition

 


  

\d view-name

  

Show view definition

 


  

\d sequence-name

  

Show sequence   definition

 


  

\dp

  

List all privileges

 


  

\dl

  

List all large objects

 


  

\da

  

List all aggregates

 


  

\df

  

List all functions

 


  

\dc

  

List all conversions

 


  

\dC

  

List all casts

 


  

\df function-name

  

List all functions   with given name

 


  

\do

  

List all operators

 


  

\do operator-name

  

List all operators   with given name

 


  

\dT

  

List all types

 


  

\dD

  

List all domains

 


  

\dg

  

List all groups

 


  

\du

  

List all users

 


  

\l

  

List all databases in   this cluster

 






















































Comments











Post a Comment






























Popular posts from this blog









How to find the  server is whether standby (slave) or primary(master) in Postgresql replication ?















  Method 1   You can check the mode of the server using "pg_controldata".  [pgsql@test~]$ pg_controldata /usr/local/pgsql/data84/  Database cluster state:               in archive recovery   --> This is Standby  Database  Database cluster state:               in production  --> This is Production Database [Master]    Method 2  You can use  pg_is_in_recovery()  which returns True  if recovery is still in progress(so the server is running in standby mode or slave)  postgres=# select pg_is_in_recovery(); pg_is_in_recovery ------------------- t (1 row)  If Return    false   so the server is running in primary mode or master   postgres=# select pg_is_in_recovery(); pg_is_in_recovery ------------------- f (1 row)    








Read more










7 Steps to configure BDR replication in postgresql 














Image







   The  BDR  (Bi-Directional Replication) project adds multi-master replication to PostgreSQL 9.4.    Postgres-BDR  has a lower impact on the masters(s) than trigger-based replication  solutions. There is no write-amplification, as it does not require  triggers to write to queue tables in order to replicate writes.      Here We are using  postgres version 9.4.12 and bdr version 1.0.2. for configuring  multi master replication . Simply Following 7 steps you can configure the multi master replication in postgresql. To download the bdr in below link. .   https://github.com/2ndQuadrant/bdr/archive/bdr-pg/REL9_4_12-1.tar.gz  $ tar -xzvf REL9_4_12-1.tar.gz $ wget https://github.com/2ndQuadrant/bdr/archive/bdr-plugin/1.0.2.tar.gz  $ tar -xzvf 1.0.2.tar.gz   1. To install BDR.  $ cd ~/bdr-bdr-pg-REL9_4_12-1 $ ./configure --prefix=/usr/lib/postgresql/9.4 --enable-debug --with-openssl $ make -j4 -s install-world $ cd ~/bdr-bdr-plugin-1.0.2 $ PATH=/usr/lib/postgresql/9.4/bin:"$PATH" ./c








Read more










How to Get Table Size, Database Size, Indexes Size, schema Size, Tablespace Size, column Size in PostgreSQL Database 















 In this post, I am sharing few important function for finding the size of database, table and index in PostgreSQL. Finding object size in postgresql database is very important and common. Is it very useful to know the exact size occupied by the object at the tablespace. The object size in the following scripts is in GB. The scripts have been formatted to work very easily with PUTTY SQL Editor. 1. Checking table size excluding table dependency: SELECT pg_size_pretty(pg_relation_size('mhrordhu_shk.mut_kharedi_audit'));  pg_size_pretty ----------------  238 MB (1 row)  2. Checking table size including table dependency: SELECT pg_size_pretty(pg_total_relation_size('mhrordhu_shk.mut_kharedi_audit'));  pg_size_pretty ----------------  268 MB (1 row)  3. Finding individual postgresql database size SELECT pg_size_pretty(pg_database_size('db_name'));  4. Finding individual table size for postgresql database -including dependency index: SELECT pg_size_pretty(pg_total_rel








Read more










PostgreSQL Introduction















  PostgreSQL tutorial provides basic and advanced concepts of SQL. Our PostgreSQL tutorial is designed for beginners and professionals.  PostgreSQL is an opens-source object-relational database management system (ORDBMS).  Our PostgreSQL tutorial includes all topics of PostgreSQL language such as create database, create table, drop database, drop table, select database, select table, insert record, update record, delete record, triggers, functions, procedures, cursors etc. There are also given PostgreSQL interview questions and quizzes to help you better understand the PostgreSQL language.    Prerequisite:  Before you start doing practice with various types of examples given in this reference, I'm making an assumption that you are already aware about what is database, especially RDBMS and what is a computer programming language.  you must have the basic knowledge of SQL   Problem:  We assure that you will not find any problem in this PostgreSQL tutorial. But if there is any mistake








Read more










ERROR:  operator does not exist: text ->> unknown LINE 1: ...stomer' as customer_name,sales_info ->>'PRODUCTS' ->>'produc...                                                              ^ HINT:  No operator matches the given name and argument type(s). You might need to add explicit type casts.















   postgres=# select * from sales;  id |                                    sales_info                                     ----+----------------------------------------------------------------------------------   1 | { "customer": "NIJAM", "PRODUCTS": {"product_name": "choclate","total_item": 6}}   2 | { "customer": "ABU", "PRODUCTS": {"product_name": "badam","total_item": 5}}   3 | { "customer": "UMAR", "PRODUCTS": {"product_name": "mobile","total_item": 1}} (3 rows)  postgres=# SELECT sales_info ->>'customer' as customer_name,sales_info ->>'PRODUCTS' ->>'product_name'  as name_of_product from sales where sales_info ->>'customer'='UMAR'; ERROR:  operator does not exist: text ->> unknown LINE 1: ...stomer' as customer_name,sales_info -&








Read more