X-Original-To: pgsql-sql@postgresql.org Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 342CE474E61 for ; Mon, 3 Mar 2003 00:09:28 -0500 (EST) Received: from postgresql.org ([64.49.215.8]) by localhost (postgresql.org [64.49.215.8:10024]) (amavisd-new) with SMTP id 56184-01 for ; Mon, 3 Mar 2003 00:09:26 -0500 (EST) Received: from zzz.zzz (unknown [212.57.173.216]) by postgresql.org (Postfix) with ESMTP id DC55C474E42 for ; Mon, 3 Mar 2003 00:09:23 -0500 (EST) Date: Mon, 3 Mar 2003 10:03:52 +0500 From: Denis Zaitsev To: Tom Lane Cc: pgsql-sql@postgresql.org Subject: Re: default operator class (PostgreSQL's error?) Message-ID: <20030303100352.D4208@natasha.zzz.zzz> References: <20030302142401.B4208@natasha.zzz.zzz> <18747.1046628100@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <18747.1046628100@sss.pgh.pa.us>; from tgl@sss.pgh.pa.us on Sun, Mar 02, 2003 at 01:01:40PM -0500 X-Virus-Scanned: by amavisd-new X-Archive-Number: 200303/56 X-Sequence-Number: 12096 I've found a reason! It's some namespace problem - there are other tho name_ops operator classes exist. My becomes third. All are the default for (their) type. And somewhere there is the issue. Renaming my operator class into, say, name_t_ops resolves the problem. Thanks for the info.