Database Schema

Schemas are analogous to directories at the operating system level, except that schemas cannot be nested.

Typical schemas usage scenarios:

• To allow many users to use one database without interfering with each other.
• To organize database objects into logical groups to make them more manageable.
• Third-party applications can be put into separate schemas so they do not collide with the names of other objects.

See also

• PostgreSQL: pg_dump, pg_restore, pgAdmin, pg_config, psql, pg_ctl, pg_isready, initdb, Role, Schema, DBeaver, Navicat, DataGrip, OmniDB, Adminer, docker-compose.xml PostgreSQL, PostgreSQL version, PostgreSQL logs, postgresql.conf, pg_hba.conf, $HOME/.pg_service.conf, Create database (PostgreSQL), Create user, createdb, GRANT, pg_stat, PostgreSQL VACUUM, EXPLAIN, pg stat activity, Autovacuum, ALTER DATABASE, PostgreSQL statistics collector, Shared buffers, EXPLAIN (PostgreSQL), EXPLAIN ANALYZE, Bitmap scan, EXPLAIN VERBOSE, EXPLAIN VERBOSE (PostgresSQL), WAL, ALTER USER, CREATE ROLE, CREATE USER, \du, show users, \l, The Statistics Collector, pganalyze, cron.schedule, Master, pg_tables, PostgreSQL replication, CREATE, SET, TOAST, PgBouncer, Restore DB, Index, meta-commands, Table, foreign table, Schema, Sequence, Views, materialized view, Table Partitioning, monitoring, PostgreSQL System Administration Functions, PostgreSQL extension, privileges, logging, PGTune, PostgreSQL parameter tunning, PostgreSQL modules, pgbench, PostgreSQL users, catalogs

https://www.postgresql.org/docs/current/ddl-schemas.html