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 Configure User Equivalence (Key-Based Authentication)  on Linux















  Installation   The SSH service should already be installed, but if it is not, install it from a Yum repository using the following command.  # yum install openssh-server   Turn on the SSH service and make sure it starts automatically on reboot.  # service sshd start # chkconfig sshd on   The SSH service is configured using the "/etc/ssh/sshd_config" file. Configuration changes have to be followed by a restart of the service.  # service sshd restart # # or # service sshd reload   Firewall   The server must have the TCP port 22 open. This can be achieved by adding the following entry to the type of firewall script described  here .  # Open port for NTP server. iptables -A INPUT -p tcp --dport 22 -j ACCEPT   SELinux   If you are using SELinux, you will need to consider the following points.   The SELinux booleans associated with the SSH service are displayed using the  getsebool  command.  # getsebool -a | grep ssh allow_ssh_keysign --> off fenced_can_ssh --> off ssh...








Read more










 PostgreSQL - Access Oracle Database in PostgreSQL















          Today, organizations stores information(data) in different database systems. Each database system has a set of applications that run against it. This data is just bits and bytes on a file system - and only a database can turn the bits and bytes of data into business information. Integration and consolidation of such information(data) into one database system is often difficult. Because many of the applications that run against one database may not have an equivalent application that runs against another. To consolidate the information into one database system, we need a heterogeneous database connection.  In this post, I'll demo on how you may connect PostgreSQL to one of heterogeneous database Oracle using different methods. Below are few methods to make connection to Oracle database in PostgreSQL. Using ODBC Driver Using Foreign DataWrappers Using Oracle Call Interface(OCI) Driver Softwares used in demo(included download links): CentOS 7 64bit,...








Read more










VMWARE WORKSTATION 3,4,5,6,7,8,9,10,11,12,14,15...etc  LICENSE KEYS COLLECTION














Image







  Below tutorialdba.com collected and sorted out hundreds of universal License Keys for all major versions of VMware Workstation Pro (not for VMware Workstation Player) 4.x, 5.x, 6.x, 7.x, 8.x, 9.x, 10.x, 11.x, 12.x and v14.x on Windows and Linux platforms (support both 32-bit and 64-bit operating system) in this single post. Besides, we also provide some license keys for VMware other projects. Just enjoy and share them.     // 4~14 Universal License Keys //   Version License Keys  VMware Workstation  VMware Workstation 4.x.x  ZHDH1-UR90N-W844G-4PTN6  G1NP0-T88AL-M016F-4P8N2  ZC14J-4U16A-0A04G-4MEZP  J1WF8-58LDE-881DG-4M8Q3    VMware Workstation 5.x.x  LUXRM-WP0DN-A256U-4M9Q3  DJXDR-NDT27-Y2NDU-4YTZK  DA925-HP80U-Z8HDC-4WXXP  3KW2W-AYR2C-88M6F-4MDQ2    VMware Workstation 6.x.x  A0E8R-YUDFV-6AK2F-4GAN2  CRX0D-VWL0V-7CJ6C-46C7A  NA8RX-QPNDU-D2LA9-4WAZL  1H4WM-N21FZ-7GK2A-44U5U  6AJ6N-THY2P-42KEF-4WTFG  FK8R9-LPCDT-88H4Y-4WRN3  KAR8R-T8MAL-K8J6A-4WDXQ  YJEKW-JMFF4-YA1DC-4WTQ...








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










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