From 336297e67675eb7e6bd277dee4542da260742459 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Wed, 22 Oct 2003 03:50:27 +0000 Subject: [PATCH] Another example-to-documentation difference. Maybe we can find a better way to keep these in sync... --- doc/src/sgml/xoper.sgml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/src/sgml/xoper.sgml b/doc/src/sgml/xoper.sgml index 80e6793397..39c49d4036 100644 --- a/doc/src/sgml/xoper.sgml +++ b/doc/src/sgml/xoper.sgml @@ -1,5 +1,5 @@ @@ -41,7 +41,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/xoper.sgml,v 1.27 2003/10/21 22:51:14 tgl E CREATE FUNCTION complex_add(complex, complex) RETURNS complex AS 'filename', 'complex_add' - LANGUAGE C; + LANGUAGE C IMMUTABLE STRICT; CREATE OPERATOR + ( leftarg = complex, @@ -113,7 +113,7 @@ SELECT (a + b) AS c FROM test_complex; - The left operand type of a commuted operator is the same as the + The left operand type of a commutable operator is the same as the right operand type of its commutator, and vice versa. So the name of the commutator operator is all that PostgreSQL needs to be given to look up the commutator, and that's all that needs to @@ -132,7 +132,7 @@ SELECT (a + b) AS c FROM test_complex; tab2.y = tab1.x, because the indexscan machinery expects to see the indexed column on the left of the operator it is given. PostgreSQL will not simply - assume that this is a valid transformation --- the definer of the + assume that this is a valid transformation --- the creator of the = operator must specify that it is valid, by marking the operator with commutator information.