Skip to content

Commit 6f53e66

Browse files
committed
doc: add examples of creative use of unique expression indexes
Unique expression indexes can constrain data in creative ways, so show two examples. Reported-by: Tuomas Leikola Discussion: https://postgr.es/m/156760275564.1127.12321702656456074572@wrigleys.postgresql.org Backpatch-through: 9.4
1 parent df189f3 commit 6f53e66

File tree

1 file changed

+19
-0
lines changed

1 file changed

+19
-0
lines changed

doc/src/sgml/indices.sgml

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -710,6 +710,15 @@ CREATE INDEX test1_lower_col1_idx ON test1 (lower(col1));
710710
</programlisting>
711711
</para>
712712

713+
<para>
714+
Expression indexes also allow control over the scope of unique indexes.
715+
For example, this unique index prevents duplicate integer values from
716+
being stored in a <type>double precision</type>-typed column:
717+
<programlisting>
718+
CREATE UNIQUE INDEX test1_uniq_int ON tests ((floor(double_col)))
719+
</programlisting>
720+
</para>
721+
713722
<para>
714723
If we were to declare this index <literal>UNIQUE</>, it would prevent
715724
creation of rows whose <literal>col1</> values differ only in case,
@@ -949,6 +958,16 @@ CREATE UNIQUE INDEX tests_success_constraint ON tests (subject, target)
949958
This is a particularly efficient approach when there are few
950959
successful tests and many unsuccessful ones.
951960
</para>
961+
962+
<para>
963+
This index allows only one null in the indexed column by using a
964+
partial index clause to process only null column values, and using
965+
an expression index clause to index <literal>true</literal> instead
966+
of <literal>null</literal>:
967+
<programlisting>
968+
CREATE UNIQUE INDEX tests_target_one_null ON tests ((target IS NULL)) WHERE target IS NULL;
969+
</programlisting>
970+
</para>
952971
</example>
953972

954973
<para>

0 commit comments

Comments
 (0)