From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Chris Hoover <revoohc(at)gmail(dot)com> |
Cc: | "pgsql-admin(at)postgresql(dot)org Admin" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: 8.2.4 Won't Build 8.1 Functional Indexes |
Date: | 2007-06-06 19:54:59 |
Message-ID: | 20070606195459.GH11800@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Chris Hoover escribió:
> I am testing upgrades to 8.2.4 from 8.1.3 and am having problems with
> 8.2.4balking at the functional indexes I have created. These indexes
> exist and
> work fine in 8.1.3, so why is 8.2.4 rejecting them?
>
> Index 1:
> CREATE INDEX acceptedbilling_to_date_accepted_billing_dt_idx
> ON acceptedbilling
> USING btree
> (to_date(accepted_billing_dt::text, 'yyyymmdd'::text));.
>
> Reject:
> ERROR: functions in index expression must be marked IMMUTABLE
> SQL state: 42P17
You can't do this because to_date and other functions are not immutable.
8.2 seems to be more picky about this -- the date conversions of
timestamptz columns are dependent on the current timezone. Perhaps you
could change this to avoid this kind of conversions, doing things like
create index foo on bar
(to_date(accepted_billing_dt at time zone 'GMT'), 'yyymmdd')
I am not sure if this actually works -- but you would need to change the
queries as well. The point is that the time zone is now fixed, instead
of being dependent on a GUC variable.
--
Alvaro Herrera http://www.amazon.com/gp/registry/DXLWNGRJD34J
"I think my standards have lowered enough that now I think 'good design'
is when the page doesn't irritate the living f*ck out of me." (JWZ)
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Hoover | 2007-06-06 21:07:23 | How to tell how long server has been up? |
Previous Message | Andrew Sullivan | 2007-06-06 19:51:01 | Re: the right time to vacuum database? |