Skip to content

Commit d391f6d

Browse files
committed
doc: CREATE DATABASE doesn't copy db-level perms. from template
Reported-by: david@kapitaltrading.com Discussion: https://postgr.es/m/166007719137.995877.13951579839074751714@wrigleys.postgresql.org Backpatch-through: 11
1 parent 7751352 commit d391f6d

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

doc/src/sgml/manage-ag.sgml

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -213,6 +213,12 @@ createdb -O <replaceable>rolename</replaceable> <replaceable>dbname</replaceable
213213
action being taken when those databases are created.
214214
</para>
215215

216+
<para>
217+
However, <command>CREATE DATABASE</command> does not copy database-level
218+
<command>GRANT</command> permissions attached to the source database.
219+
The new database has default database-level permissions.
220+
</para>
221+
216222
<para>
217223
There is a second standard system database named
218224
<literal>template0</literal>.<indexterm><primary>template0</primary></indexterm> This

0 commit comments

Comments
 (0)
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy