Received: from localhost.localdomain (postgresql.org [64.49.215.8]) by localhost (Postfix) with ESMTP id DBCDB4762FA for ; Wed, 5 Jun 2002 14:56:57 -0400 (EDT) Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250]) by postgresql.org (Postfix) with ESMTP id B7B66475D51 for ; Wed, 5 Jun 2002 14:53:00 -0400 (EDT) Received: from [66.219.92.2] (HELO chocolate-mousse) by davinci.ethosmedia.com (CommuniGate Pro SMTP 3.5.9) with ESMTP id 1500428; Wed, 05 Jun 2002 11:53:00 -0700 Content-Type: text/plain; charset="iso-8859-1" From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: Richard Poole , pgsql-sql@postgresql.org Subject: Re: Indexing Metaphone? Date: Wed, 5 Jun 2002 11:53:32 -0700 X-Mailer: KMail [version 1.4] References: <200206051112.02090.josh@agliodbs.com> <20020605183950.GA25470@guests.deus.net> In-Reply-To: <20020605183950.GA25470@guests.deus.net> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200206051153.32511.josh@agliodbs.com> X-Archive-Number: 200206/43 X-Sequence-Number: 8008 Richard, > That's the error message you'd get if pg just didn't know of any > function called "metaphone". Have you done the appropriate CREATE > FUNCTION magic? "\df metaphone" in psql will tell you whether it's > heard of it or not. Yup: jwnet=3D> \df metaphone List of functions Result data type | Name | Argument data types ------------------+-----------+--------------------- text | metaphone | text, integer (1 row) --=20 -Josh Berkus