doc: Improve CREATE COLLATION locking documentation

Move out of the concurrency control chapter, where mostly only user
table locks are discussed, and move to CREATE COLLATION reference page.

Author: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>
Author: Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>
This commit is contained in:
Peter Eisentraut 2018-07-30 22:01:04 +02:00
parent c0a552921b
commit 70de0abdb7
2 changed files with 8 additions and 2 deletions

View File

@ -970,8 +970,7 @@ ERROR: could not serialize access due to read/write dependencies among transact
</para>
<para>
Acquired by <command>CREATE COLLATION</command>,
<command>CREATE TRIGGER</command>, and many forms of
Acquired by <command>CREATE TRIGGER</command> and many forms of
<command>ALTER TABLE</command> (see <xref linkend="sql-altertable"/>).
</para>
</listitem>

View File

@ -162,6 +162,13 @@ CREATE COLLATION [ IF NOT EXISTS ] <replaceable>name</replaceable> FROM <replace
<refsect1 id="sql-createcollation-notes">
<title>Notes</title>
<para>
<command>CREATE COLLATION</command> takes a <literal>SHARE ROW
EXCLUSIVE</literal> lock, which is self-conflicting, on the
<structname>pg_collation</structname> system catalog, so only one
<command>CREATE COLLATION</command> command can run at a time.
</para>
<para>
Use <command>DROP COLLATION</command> to remove user-defined collations.
</para>