Re: Why extract( ... from timestamp ) is not immutable? - Mailing list pgsql-general

From Adrian Klaver
Subject Re: Why extract( ... from timestamp ) is not immutable?
Date
Msg-id 201201251604.45680.adrian.klaver@gmail.com
Whole thread Raw
In response to Re: Why extract( ... from timestamp ) is not immutable?  (hubert depesz lubaczewski <depesz@depesz.com>)
List pgsql-general
On Wednesday, January 25, 2012 2:46:39 pm hubert depesz lubaczewski wrote:
> On Wed, Jan 25, 2012 at 02:07:40PM -0800, Adrian Klaver wrote:
> > Finally dawned on me. When you use 'at time zone' on a timestamp
> > with tz it strips the tz which then allows the value to be indexed
> > because:
> >
> > -[ RECORD 5
> > ]-------+---------------------------------------------------------------
> > ---------- Schema              | pg_catalog
> > Name                | date_part
> > Result data type    | double precision
> > Argument data types | text, timestamp without time zone
> > Type                | normal
> > Volatility          | immutable
> > Owner               | postgres
> > Language            | internal
> > Source code         | timestamp_part
> > Description         | extract field from timestamp
>
> yes, but it is not correct - the value is actually stable, and not
> immutable.

Alright, because the epoch and timezone* fields do timezone manipulation on the
supplied values. Well learned a lot. Thanks.

>
> Best regards,
>
> depesz

--
Adrian Klaver
adrian.klaver@gmail.com

pgsql-general by date:

Previous
From: Nick
Date:
Subject: How to know if update is from a foreign key cascade in plperl?
Next
From: Leguevaques Alex
Date:
Subject: Composite Type : pros and cons