Re: date_trunc() in a specific time zone
| От | Steve Crawford |
|---|---|
| Тема | Re: date_trunc() in a specific time zone |
| Дата | |
| Msg-id | CAEfWYyzr2VUZWjSAm6Q3iknhuKGQLO1uqnEFPZusfpcWRymv2w@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: date_trunc() in a specific time zone (Vik Fearing <vik.fearing@2ndquadrant.com>) |
| Ответы |
Re: date_trunc() in a specific time zone
|
| Список | pgsql-hackers |
On Mon, Oct 29, 2018 at 8:44 AM Vik Fearing <vik.fearing@2ndquadrant.com> wrote:
On 29/10/2018 16:26, Andreas Karlsson wrote:
> On 10/29/2018 04:18 PM, Vik Fearing wrote:
>> A use case that I see quite a lot of is needing to do reports and other
>> calculations on data per day/hour/etc but in the user's time zone. The
>> way to do that is fairly trivial, but it's not obvious what it does so
>> reading queries becomes just a little bit more difficult.
>
> Hm, I am not sure if I see any major win from writing
>
> date_trunc('day', timestamptz '2001-02-16 20:38:40+00', 'Australia/Sydney')
>
> instead of
>
> date_trunc('day', timestamptz '2001-02-16 20:38:40+00' AT TIME ZONE
> 'Australia/Sydney')
Because I don't want '2001-02-16 00:00:00' (where?), I want the precise
moment in time that that represents ('2001-02-16 13:00:00+00') so I can
pull the correct rows out of my big table.
This isn't for display purposes.
I'm a bit confused as to the use case. Wouldn't someone who wants locally-based time-period ranges also want output displayed in the corresponding zone both of which are already well handled in one place by "set timezone..."?
Cheers,
Steve
В списке pgsql-hackers по дате отправления: