Re: contrib/pgcrypto functions not IMMUTABLE?

Marko Kreen wrote:
> On Sun, Jul 03, 2005 at 07:54:47AM -0600, Michael Fuhr wrote:
>>In the functions marked STRICT, should I leave the PG_ARGISNULL()
>>checks in place as a precaution?  Removing those checks could cause
>>problems if people use the new code but have old (non-STRICT) catalog
>>entries.
> 
> Good point.  Let them be.

Assuming the STRICT / IMMUTABLE changes are only going into HEAD, you 
can safely remove the PG_ARGISNULL() checks -- people upgrading from a 
prior version of Postgres (and therefore pgcrypto) will need to dump and 
reload anyway.

-Neil