diff options
Diffstat (limited to 'doc/src/sgml/ref/create_aggregate.sgml')
| -rw-r--r-- | doc/src/sgml/ref/create_aggregate.sgml | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/src/sgml/ref/create_aggregate.sgml b/doc/src/sgml/ref/create_aggregate.sgml index 24e233f589..70362f6503 100644 --- a/doc/src/sgml/ref/create_aggregate.sgml +++ b/doc/src/sgml/ref/create_aggregate.sgml @@ -1,5 +1,5 @@ <!-- -$PostgreSQL: pgsql/doc/src/sgml/ref/create_aggregate.sgml,v 1.32 2005/04/12 04:26:15 tgl Exp $ +$PostgreSQL: pgsql/doc/src/sgml/ref/create_aggregate.sgml,v 1.33 2005/11/04 23:14:02 petere Exp $ PostgreSQL documentation --> @@ -143,11 +143,11 @@ SELECT col FROM tab ORDER BY col USING sortop LIMIT 1; </programlisting> Further assumptions are that the aggregate ignores null inputs, and that it delivers a null result if and only if there were no non-null inputs. - Ordinarily, a datatype's <literal><</> operator is the proper sort + Ordinarily, a data type's <literal><</> operator is the proper sort operator for <function>MIN</>, and <literal>></> is the proper sort operator for <function>MAX</>. Note that the optimization will never - actually take effect unless the specified operator is the LessThan or - GreaterThan strategy member of a btree index opclass. + actually take effect unless the specified operator is the <quote>less than</quote> or + <quote>greater than</quote> strategy member of a B-tree index operator class. </para> </refsect1> @@ -243,7 +243,7 @@ SELECT col FROM tab ORDER BY col USING sortop LIMIT 1; The associated sort operator for a <function>MIN</>- or <function>MAX</>-like aggregate. This is just an operator name (possibly schema-qualified). - The operator is assumed to have the same input datatypes as + The operator is assumed to have the same input data types as the aggregate. </para> </listitem> |