| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Eric G(dot) Miller" <egm2(at)jps(dot)net> |
| Cc: | PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Bug with timestamp !!! |
| Date: | 2001-05-13 15:27:45 |
| Message-ID: | 3449.989767665@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-bugs pgsql-general |
"Eric G. Miller" <egm2(at)jps(dot)net> writes:
> While I don't see such dramatic results with this bad input data, I did
> run across something a little peculiar:
With what PG version? On what platform?
Comparing 7.1.1 against 7.0.*, I note that the resolution of "illegal"
times during a DST jump has changed, at least on my platform (HPUX 10.20).
7.0.* resolves the time backwards whereas current sources resolve
forwards: "select timestamp('2001-04-01 02:02:02')" yields
2001-04-01 01:02:02-05 in 7.0.2
2001-04-01 03:02:02-04 in current
Since this is dependent on how the local mktime() library routine
reacts to "illegal" times, some platform-to-platform variation is to be
expected. Your example looks like mktime() must actually have some
internal state on your machine, causing its result to depend on what
it was asked previously :-(
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rainer Mager | 2001-05-13 22:55:38 | Postgres <-> Oracle |
| Previous Message | Eric G. Miller | 2001-05-13 05:56:51 | Re: Bug with timestamp !!! |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Trond Endrestøl | 2001-05-13 16:24:22 | Bug in configure.in, minor annoyance, PostgreSQL 7.2devel & FreeBSD 2.2.8 |
| Previous Message | Eric G. Miller | 2001-05-13 05:56:51 | Re: Bug with timestamp !!! |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ed Loehr | 2001-05-13 15:35:28 | Re: [PATCHES] Re: microsecond log timestamps |
| Previous Message | Tom Lane | 2001-05-13 15:12:55 | Re: [PATCHES] Re: microsecond log timestamps |