summaryrefslogtreecommitdiff
path: root/doc/src/sgml/citext.sgml
diff options
context:
space:
mode:
Diffstat (limited to 'doc/src/sgml/citext.sgml')
-rw-r--r--doc/src/sgml/citext.sgml15
1 files changed, 12 insertions, 3 deletions
diff --git a/doc/src/sgml/citext.sgml b/doc/src/sgml/citext.sgml
index 43ebd25958..49b0989815 100644
--- a/doc/src/sgml/citext.sgml
+++ b/doc/src/sgml/citext.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/citext.sgml,v 1.2 2008/09/12 18:29:49 tgl Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/citext.sgml,v 1.4 2010/06/29 22:29:13 momjian Exp $ -->
<sect1 id="citext">
<title>citext</title>
@@ -58,8 +58,8 @@
The <type>citext</> data type allows you to eliminate calls
to <function>lower</> in SQL queries, and allows a primary key to
be case-insensitive. <type>citext</> is locale-aware, just
- like <type>text</>, which means that the comparison of uppercase and
- lowercase characters is dependent on the rules of
+ like <type>text</>, which means that the comparison of upper case and
+ lower case characters is dependent on the rules of
the <literal>LC_CTYPE</> locale setting. Again, this behavior is
identical to the use of <function>lower</> in queries. But because it's
done transparently by the datatype, you don't have to remember to do
@@ -205,6 +205,15 @@
will need two indexes if you want both types of searches to be fast.
</para>
</listitem>
+
+ <listitem>
+ <para>
+ The schema containing the <type>citext</> operators must be
+ in the current <varname>search_path</> (typically <literal>public</>);
+ if it is not, a normal case-sensitive <type>text</> comparison
+ is performed.
+ </para>
+ </listitem>
</itemizedlist>
</sect2>