Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 2BBB19FB6CA for ; Fri, 9 Mar 2007 09:14:25 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-new, port 10024) with ESMTP id 76867-08 for ; Fri, 9 Mar 2007 09:14:18 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.4 Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.225]) by postgresql.org (Postfix) with ESMTP id 4AD099FB974 for ; Fri, 9 Mar 2007 09:14:18 -0400 (AST) Received: by wx-out-0506.google.com with SMTP id i28so859421wxd for ; Fri, 09 Mar 2007 05:14:17 -0800 (PST) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=KFm3UfYBKpyinHgQ8g1PPDj+q5T2HGeAGyJADgIsezz51dVjlE0PImxIC+/RAGGwhCJp4u5GpDyTcT9bPtpuXf9uX+NWWnDJKEqZ/F6zhZq9hQBhbMGAZoTJfcXlDHXcOyrzVUS1kj7ab9Rv6ZZ84YFOj5J4jU14+8DyNlGKPN4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=SEwFGRXfOOxWU3g7kKWTZ4X5NXHFnx646y4zX1r7Qy8hRej4z2Caz19EkxqG4me+098ZYMmGRJlwktwRdUZwlfBuwxCaNM7vDQNE5myDbruT2QB/QLoUv9zQivx3CQ4VW+cmsbHN+y6RKgoc4R3Ya/DjBd9V6xBh0WmfNgzAo/4= Received: by 10.70.39.11 with SMTP id m11mr2909006wxm.1173446057074; Fri, 09 Mar 2007 05:14:17 -0800 (PST) Received: by 10.49.75.11 with HTTP; Fri, 9 Mar 2007 05:14:16 -0800 (PST) Message-ID: <81961ff50703090514k562d1218rd44df84a13d69507@mail.gmail.com> Date: Fri, 9 Mar 2007 08:14:16 -0500 From: "Chad Wagner" To: "Ezequias Rodrigues da Rocha" Subject: Re: SHA-1 vs MD5 Cc: PostgreSQL In-Reply-To: <55c095e90703090434ob874f2q4ff3cfd0d91c88f3@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_1405_4647960.1173446056866" References: <55c095e90703071204t5aebb921s9d5f1067d3c2f035@mail.gmail.com> <81961ff50703071344i28d9ea6cr4902fed404b38602@mail.gmail.com> <55c095e90703080339y67152f49ud82741fd21ac6370@mail.gmail.com> <81961ff50703080652o41274e2djc5b789fb4da9bd27@mail.gmail.com> <55c095e90703090434ob874f2q4ff3cfd0d91c88f3@mail.gmail.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200703/101 X-Sequence-Number: 27739 ------=_Part_1405_4647960.1173446056866 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline On 3/9/07, Ezequias Rodrigues da Rocha wrote: > > Thank you so much for your information. I installed the pgCrypto. Now I > have more than 40 functions (i believe all are from pgcrypto) but when I try > to run your query: > > select encode(digest('blahblah', 'sha256'), 'hex'); > > I got the error: > > ERROR: Cannot use "sha256": No such hash algorithm > SQL state: 22023 > It may not be available in your version of the database/pgcrypto module, my test was performed on 8.2.3. ------=_Part_1405_4647960.1173446056866 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On 3/9/07, Ezequias Rodrigues da Rocha <ezequias.rocha@gmail.com> wrote:
Thank you so much for your information. I installed the pgCrypto. Now I have more than 40 functions (i believe all are from pgcrypto) but when I try to run your query:

select encode(digest('blahblah', 'sha256'), 'hex');

I got the error:

ERROR: Cannot use "sha256": No such hash algorithm
SQL state: 22023


It may not be available in your version of the database/pgcrypto module, my test was performed on 8.2.3.
------=_Part_1405_4647960.1173446056866--