On Thu, Aug 13, 2009 at 08:30:07AM -0700, Scott Bailey wrote: > >On Wed, Aug 12, 2009 at 08:45:58PM -0700, Scott Bailey wrote: > >>CREATE OR REPLACE FUNCTION unnest(anyarray) > >> RETURNS SETOF anyelement AS > >>$BODY$ > >>SELECT $1[i] FROM > >> generate_series(array_lower($1,1), > >> array_upper($1,1)) i; > >>$BODY$ > >> LANGUAGE 'sql' IMMUTABLE STRICT > > > >I'd recommend taking off the "STRICT" from this. It will, counter > >intuitively, slow things down when you're not expecting it. > > Woah! Really? I use strict a lot when it doesn't make sense to process a > function with a null param. Can you give me more details or point me to > more reading on this issue? Thanks. There have been a few to-and-fros between me and other people about this. It's basically awkward interaction with the optimizer not being able to expand this out because it may change behavior. Try: http://archives.postgresql.org/pgsql-general/2009-06/msg00233.php IMMUTABLE is good though, don't go removing that yet! -- Sam http://samason.me.uk/ -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
