From f71fb9e0b87a9b32660cbe40577135e79d7f1d0e Mon Sep 17 00:00:00 2001
From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Tue, 28 Mar 2000 02:51:09 +0000
Subject: [PATCH] Add a little to index operator class discussion.
---
doc/src/sgml/indices.sgml | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/doc/src/sgml/indices.sgml b/doc/src/sgml/indices.sgml
index 8dc410f263a..32aa5e7892e 100644
--- a/doc/src/sgml/indices.sgml
+++ b/doc/src/sgml/indices.sgml
@@ -110,9 +110,11 @@
integers. In practice the default operator class for the field's
datatype is usually sufficient. The main point of having operator classes
is that for some datatypes, there could be more than one meaningful
- ordering. For an index on such a datatype, we could select which
- ordering we wanted by selecting the proper operator class. There
- are also some operator classes with special purposes:
+ ordering. For example, we might want to sort a complex-number datatype
+ either by absolute value or by real part. We could do this by defining
+ two operator classes for the datatype and then selecting the proper
+ class when making an index. There are also some operator classes with
+ special purposes:
<itemizedlist>
<listitem>
--
GitLab