| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: diferent timezones in the same table? |
| Date: | 2009-09-25 14:29:24 |
| Message-ID: | 19831.1253888964@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec> writes:
> One of the tables in a client production system has several timestamp
> with time zone fields, in one of those fields they store '1900-01-01
> 00:00:00'::timestamp with time zone where there is no valid value (a
> legacy from another dbms)...
This will be interpreted as 1900-01-01 00:00:00 in whatever timezone
is selected when you insert the value...
> timezone 'America/Guayaquil'
... and in that zone, times before 1931 are taken to be local mean
solar time, which is 5 hours and change off GMT. See the Olsen data
files:
# Zone NAME GMTOFF RULES FORMAT [UNTIL]
Zone America/Guayaquil -5:19:20 - LMT 1890
-5:14:00 - QMT 1931 # Quito Mean Time
-5:00 - ECT # Ecuador Time
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | smuffy | 2009-09-25 15:50:37 | BUG #5082: I can't get logfile( achive ) |
| Previous Message | Jaime Casanova | 2009-09-25 14:19:41 | diferent timezones in the same table? |