Received: from ll.mit.edu (LLMAIL.LL.MIT.EDU [129.55.12.40]) by postgresql.org (Postfix) with ESMTP id C6273476958 for ; Sat, 16 Mar 2002 13:28:12 -0500 (EST) Received: (from smtp@localhost) by ll.mit.edu (8.11.3/8.8.8) id g2GIS1c13874 for ; Sat, 16 Mar 2002 13:28:01 -0500 (EST) Received: from UNKNOWN( ), claiming to be "sty" via SMTP by llmail, id smtpdAAAxba4YA; Sat Mar 16 13:28:00 2002 Date: Sat, 16 Mar 2002 13:28:00 -0500 From: george young To: pgsql-sql@postgresql.org Subject: hashtext function disappears in 7.2? Message-Id: <20020316132800.4a414187.gry@ll.mit.edu> Reply-To: gry@ll.mit.edu Organization: MIT Lincoln Laboratory X-Mailer: Sylpheed version 0.7.0 (GTK+ 1.2.8; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Archive-Number: 200203/213 X-Sequence-Number: 7092 Since I upgraded from 7.0.3 to 7.2, I can't find the sql function "hashtext". Why has it been discontinued? Is there some alternate new way to take a text value and get an unique integer? I use this as an argument to the contributed (and invaluable!) user_write_lock_oid(int) function to manage advisory locks on arbitrary named objects. -- George -- I cannot think why the whole bed of the ocean is not one solid mass of oysters, so prolific they seem. Ah, I am wandering! Strange how the brain controls the brain! -- Sherlock Holmes in "The Dying Detective"