choose an appropriate <literal>LOCALE</literal> setting
<emphasis>and</emphasis> set the collation to not deterministic here.
</para>
<para>
Nondeterministic collations are only supported with the ICU provider.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><replaceable>rules</replaceable></term>
<listitem>
<para>
Specifies additional collation rules to customize the behavior of the
collation. This is supported for ICU only. See <xref
linkend="icu-tailoring-rules"/> for details.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><replaceable>version</replaceable></term>
<listitem>
<para>
Specifies the version string to store with the collation. Normally,
this should be omitted, which will cause the version to be computed
from the actual version of the collation as provided by the operating
system. This option is intended to be used
by <command>pg_upgrade</command> for copying the version from an
existing installation.
</para>
<para>
See also <xref linkend="sql-altercollation"/> for how to handle
collation version mismatches.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><replaceable>existing_collation</replaceable></term>
<listitem>
<para>
The name of an existing collation to copy. The new collation
will have the same properties as the existing one, but it
will be an independent object.
</para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
<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>