Re: [GENERAL] Why extract( ... from timestamp ) is not immutable? - Mailing list pgsql-hackers

From Josh Berkus
Subject Re: [GENERAL] Why extract( ... from timestamp ) is not immutable?
Date
Msg-id 4F275B08.4010503@agliodbs.com
Whole thread Raw
In response to Re: [GENERAL] Why extract( ... from timestamp ) is not immutable?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [GENERAL] Why extract( ... from timestamp ) is not immutable?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 1/30/12 5:41 PM, Tom Lane wrote:
> hubert depesz lubaczewski <depesz@depesz.com> writes:
>> On Mon, Jan 30, 2012 at 10:35:21AM -0800, Josh Berkus wrote:
>>> We can't have functions which are immutable or not depending on their
>>> inputs.  That way lies madness.
> 
>> but this is exactly what's happening now.
> 
> Well, the current marking is clearly incorrect.  What to do about that
> is a bit less clear --- should we downgrade the marking, or change the
> function's behavior so that it really is immutable?

AFAIK, the only case which is NOT immutable is extract(epoch FROM
timestamp without time zone), no?

-- 
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com


pgsql-hackers by date:

Previous
From: Kyotaro HORIGUCHI
Date:
Subject: Re: Speed dblink using alternate libpq tuple storage
Next
From: Ashutosh Bapat
Date:
Subject: Re: Confusing EXPLAIN output in case of inherited tables