Re: contrib/pgcrypto functions not IMMUTABLE?

From: Michael Fuhr <mike(at)fuhr(dot)org>
To: Marko Kreen <marko(at)l-t(dot)ee>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Russell Smith <mr-russ(at)pws(dot)com(dot)au>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: contrib/pgcrypto functions not IMMUTABLE?
Date: 2005-07-04 04:29:28
Message-ID: 20050704042928.GA60958@winnie.fuhr.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Jul 03, 2005 at 08:15:07PM +0300, Marko Kreen wrote:
>
> Michael, the result is, you can make them all STRICT.

OK. Does anybody else have thoughts on removing the PG_ARGISNULL()
checks? Neil suggests removing them because they'd be unnecessary,
but I'm concerned about people who'd use the new code with old
catalog entries that aren't STRICT (e.g., restored from a dump).
Should we leave the PG_ARGISNULL() checks in place as a safety
measure, or should the 8.1 Release Notes make it clear that the
functions need to be recreated (or pg_proc updated)?

--
Michael Fuhr
http://www.fuhr.org/~mfuhr/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2005-07-04 04:43:43 Re: contrib/pgcrypto functions not IMMUTABLE?
Previous Message Tom Lane 2005-07-04 04:16:12 Re: Constraint Exclusion (Partitioning) - Initial Review