From: | Marko Tiikkaja <marko(at)joh(dot)to> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: to_char_at_timezone()? |
Date: | 2014-11-05 18:39:47 |
Message-ID: | 545A6EF3.8010008@joh.to |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 11/5/14, 7:36 PM, Josh Berkus wrote:
> On 11/04/2014 04:04 PM, Marko Tiikkaja wrote:
>> In my example, the input is a "timestamptz", and the output is converted
>> to the target time zone the same way timestamptz_out() does, except
>> based on the input timezone instead of TimeZone.
>>
>> Not sure whether it would make sense to do this for "timestamp", or
>> whether there's even a clear intuitive behaviour there.
>
> Why wouldn't we just add the timezone as an additional parameter?
Are you suggesting that we add a new overload of to_char() instead of a
new function to_char_at_timezone()? That sounds a bit confusing, but
that might just be me.
.marko
From | Date | Subject | |
---|---|---|---|
Next Message | Jim Nasby | 2014-11-05 18:40:41 | Re: pg_multixact not getting truncated |
Previous Message | Josh Berkus | 2014-11-05 18:36:12 | Re: to_char_at_timezone()? |