Re: contrib/pgcrypto functions not IMMUTABLE?

From: Russell Smith <mr-russ(at)pws(dot)com(dot)au>
To: Michael Fuhr <mike(at)fuhr(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: contrib/pgcrypto functions not IMMUTABLE?
Date: 2005-07-03 06:24:31
Message-ID: 200507031624.32350.mr-russ@pws.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, 3 Jul 2005 03:32 pm, Michael Fuhr wrote:
> I've noticed that contrib/pgcrypto/pgcrypto.sql.in doesn't include
> a volatility category in its CREATE FUNCTION statements, so the
> functions are all created VOLATILE. Shouldn't most of them be
> IMMUTABLE? Or do the algorithms have side effects? So far I've
> found no discussion about this except for one person asking about
> it last year:
>
> http://archives.postgresql.org/pgsql-admin/2004-12/msg00065.php
>
I know the salt functions MUST stay volatile, as they produce different output
every time you call them. I've not looked at the pgcrypto code, so I can't
make further comment than that.

Regards

Russell Smith.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Fuhr 2005-07-03 06:43:32 Re: contrib/pgcrypto functions not IMMUTABLE?
Previous Message Peter Eisentraut 2005-07-03 05:43:42 Re: Autotools update