| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Alban Hertroys <haramrae(at)gmail(dot)com> |
| Cc: | gkhan <drjohnpayne(at)gmail(dot)com>, <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: to_timestamp alternatives |
| Date: | 2016-01-04 23:21:51 |
| Message-ID: | 568AFE8F.6000308@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 1/1/16 7:15 AM, Alban Hertroys wrote:
>> Since you're dealing with GPS data and presumably have lat/long, it shouldn't be hard to do this dynamically either, either by just blindly dividing longitude by 15 or using actual timezone shape polygons and @> or <@.
> That would be a bad idea for global data, since not all time zones are full hours apart, or have the same (if any) DST change-over dates. For example, India is currently at UTC+05:30, probably because they wrapped the entire country in the same TZ after their independence.
The original desire was to ignore DST, hence my suggestion. Normally
you'd want to figure out the correct TZ for the lat/long.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-01-05 00:14:42 | Re: RLS 9.5rc1 configuration changes? |
| Previous Message | Ted Toth | 2016-01-04 23:09:29 | Re: RLS 9.5rc1 configuration changes? |