Re: Timestamp with vs without time zone.
От | Michael Lewis |
---|---|
Тема | Re: Timestamp with vs without time zone. |
Дата | |
Msg-id | CAHOFxGpHM8Ka+S2eTSMSR=TRA5DsQ95C+H7Ezrs5d_1UjD6HXQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Timestamp with vs without time zone. (cen <cen.is.imba@gmail.com>) |
Ответы |
Re: Timestamp with vs without time zone.
|
Список | pgsql-general |
Related to this current discussion and exchange of ideas... is there a best practice for retrieving data in such a way as the rows are localized to a timezone for where/group by purposes. That is, if I have a table which has events, but those events belong to a tenant or some entity that has a location which implies a timezone (or at least an offset), is there a best way to write a query similar to the below? Please forgive and overlook if there is some obvious syntax error, as this is just a quick and dirty example. Might it make sense to store a "localized" version of the timestamp *without* timezone on the event record such that an index can be used for fast retrieval and even grouping?
select
date_trunc( 'month', e.event_datetime AT TIMEZONE t.time_zone_name ) AS event_date,
select
date_trunc( 'month', e.event_datetime AT TIMEZONE t.time_zone_name ) AS event_date,
where e.event_datetime AT TIMEZONE t.time_zone_name >= '01/01/2021'::DATE AND e.event_datetime AT TIMEZONE t.time_zone_name < '09/01/2021'::DATE;
В списке pgsql-general по дате отправления: