Difference between revisions of "Database Schema"
Jump to navigation
Jump to search
↑ https://www.postgresql.org/docs/current/ddl-schemas.html
↑ https://www.postgresql.org/docs/current/ddl-schemas.html
↑ https://stackoverflow.com/a/10353730
↑ https://dba.stackexchange.com/questions/40045/how-do-i-list-all-schemas-in-postgresql
Line 1: | Line 1: | ||
[[wikipedia:Database schema]] are analogous to [[directories]] at the operating system level, except that schemas cannot be nested. <ref>https://www.postgresql.org/docs/current/ddl-schemas.html</ref> | [[wikipedia:Database schema]] are analogous to [[directories]] at the operating system level, except that schemas cannot be nested. <ref>https://www.postgresql.org/docs/current/ddl-schemas.html</ref> | ||
− | |||
− | |||
Typical schemas usage scenarios <ref> https://www.postgresql.org/docs/current/ddl-schemas.html</ref>: | Typical schemas usage scenarios <ref> https://www.postgresql.org/docs/current/ddl-schemas.html</ref>: | ||
* To allow many users to use one database without interfering with each other. | * To allow many users to use one database without interfering with each other. | ||
Line 7: | Line 5: | ||
* Third-party applications can be put into separate schemas so they do not collide with the names of other objects. | * Third-party applications can be put into separate schemas so they do not collide with the names of other objects. | ||
− | + | == Example == | |
* [[CREATE SCHEMA]] | * [[CREATE SCHEMA]] | ||
Revision as of 09:05, 10 October 2022
wikipedia:Database schema are analogous to directories at the operating system level, except that schemas cannot be nested. [1] Typical schemas usage scenarios [2]:
- 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.
Example
Grant examples on schemas:
GRANT USAGE ON ALL SEQUENCES IN SCHEMA your_schema TO mygrp;
[3]GRANT USAGE ON SCHEMA your_schema TO GROUP your_group;
PostgreSQL: pg_catalog
and public
.
- Show/List schemas:
select nspname from pg_catalog.pg_namespace;
select schema_name from information_schema.schemata;
[4]\dn
\dn+
GRANT SELECT ON ALL TABLES IN SCHEMA public TO xxx;
Related
- Liquibase
- PostgreSQL, Amazon Redshift
- GRANT
- Role
- PostgreSQL: catalogs
GRANT SELECT
- Index, Table, Schema, Sequence, Views
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
Advertising: