From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: to_date() marked stable? |
Date: | 2011-11-29 03:45:14 |
Message-ID: | 201111290345.pAT3jEB21598@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > I was wondering why we mark to_date() as stable and not immutable?
>
> Do you really want to guarantee that it isn't, and never will be,
> affected by timezone, datestyle, lc_time, etc? In particular it seems
> likely that somebody will eventually complain that since to_char can
> output localized month/day names according to lc_time, to_date should be
> able to read them.
>
> > Are there people using to_date in indexes or partition functions where
> > changing it to immutable would be useful?
>
> By definition, there are not, and I don't recall many complaints from
> people trying to. On the other hand, if we mark it immutable and then
> in future wish to go back to allowing environment dependencies, we will
> have to risk breaking working applications.
OK --- without user requests, it seems pointless to make a change here.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
From | Date | Subject | |
---|---|---|---|
Next Message | Etsuro Fujita | 2011-11-29 04:16:01 | Re: pgsql_fdw, FDW for PostgreSQL server |
Previous Message | Tom Lane | 2011-11-29 03:29:08 | Re: to_date() marked stable? |