DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=from:to:subject:date:user-agent:mime-version:content-type
	:content-transfer-encoding:message-id;
	b=vAcYcn9M/ukAGbumfgaluPyn/lbpIbqoRXFXHr2D9zJ9figFAKelxo6Q2KCFJomb3e
	f6sfN4YFbV5/NoPEaOC3lIUMVpMneoAJ1mvufArihXeZV+1i3BfTcLSDdzjI5UJJpu58
	NjLApOY9VSgxkfIx3lBjaXGH69/eeQfbZMvjs=
From: Marc Cousin <cousinmarc@gmail.com>
To: pgsql-docs@postgresql.org
Subject: =?iso-8859-1?q?CREATE=A0OPERATOR_and?= precedence
Date: Thu, 8 Jul 2010 16:28:30 +0200
User-Agent: KMail/1.13.5 (Linux/2.6.34-ARCH; KDE/4.4.5; x86_64; ; )
MIME-Version: 1.0
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-Id: <201007081628.30860.cousinmarc@gmail.com>

Hi,

I just got caught by a precedence problem with CREATE OPERATOR.

Obviously, it was mostly my fault (I didn't think of the precedence of my=20
operator at all), but I didn't find anything in the CREATE OPERATOR=20
documentation about it either.

=46rom looking at the code, I think I understood that it has a very low=20
precedence, but shouldn't it be specified in the documentation (so that at=
=20
least distracted people like me think of precedence next time they create a=
n=20
operator :) ) ?

Cheers

Marc