tables (and other objects) are automatically put into a schema named "public"

From: PG Doc comments form <noreply(at)postgresql(dot)org>
To: pgsql-docs(at)lists(dot)postgresql(dot)org
Cc: gary(dot)aviv(at)gmail(dot)com
Subject: tables (and other objects) are automatically put into a schema named "public"
Date: 2018-11-08 20:32:19
Message-ID: 154170913923.26250.8601986455411276596@wrigleys.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

The following documentation comment has been logged on the website:

Page: https://www.postgresql.org/docs/9.6/ddl-schemas.html
Description:

This statement is not true and is contradicted in
https://www.postgresql.org/docs/9.6/sql-createtable.html which states
correctly that:
If a schema name is given (for example, CREATE TABLE myschema.mytable ...)
then the table is created in the specified schema. Otherwise it is created
in the current schema.
It is also worth mentioning that if current_schema is empty (i.e.
,search_path is empty or contains the names of non-existent schemas) you
get the error:
ERROR: no schema has been selected to create in

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message PG Doc comments form 2018-11-10 06:08:22 The 'replication' keyword
Previous Message Bruce Momjian 2018-11-06 18:42:20 Re: effective_cache_size