Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 4a65e1c

Browse files
committed
doc: Fix description of deterministic flag of CREATE COLLATION
The documentation said that you need to pick a suitable LC_COLLATE setting in addition to setting the DETERMINISTIC flag. This would have been correct if the libc provider supported nondeterministic collations, but since it doesn't, you actually need to set the LOCALE option. Reviewed-by: Kashif Zeeshan <kashi.zeeshan@gmail.com> Discussion: https://www.postgresql.org/message-id/flat/a71023c2-0ae0-45ad-9688-cf3b93d0d65b%40eisentraut.org
1 parent 9c1d1bd commit 4a65e1c

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

doc/src/sgml/ref/create_collation.sgml

+1-1
Original file line numberDiff line numberDiff line change
@@ -154,7 +154,7 @@ CREATE COLLATION [ IF NOT EXISTS ] <replaceable>name</replaceable> FROM <replace
154154
logically equal by the comparison. PostgreSQL breaks ties using a
155155
byte-wise comparison. Comparison that is not deterministic can make the
156156
collation be, say, case- or accent-insensitive. For that, you need to
157-
choose an appropriate <literal>LC_COLLATE</literal> setting
157+
choose an appropriate <literal>LOCALE</literal> setting
158158
<emphasis>and</emphasis> set the collation to not deterministic here.
159159
</para>
160160

0 commit comments

Comments
 (0)