| From: | Nick Johnson <ctfdy(at)spatula(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: strange timezone problem |
| Date: | 2007-11-07 17:24:51 |
| Message-ID: | 20071107092324.Y46367@turing |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, 7 Nov 2007, Tom Lane wrote:
> Nick Johnson <ctfdy(at)spatula(dot)net> writes:
> > I'm using PostgreSQL 8.2.3 and seeing this behaviour with timezones:
[snip]
> > Shouldn't that second row have been in the results of the second query?
>
> Huh? Those results look perfectly sane to me.
Ah, you're right of course. Just a complete mental lapse on my part (thus
the need of a 'sanity' check).
> That's correct ... as of last year, DST extends through the first Sunday
> in November in the USA.
Twice in one morning the database was cleverer than me.
Nick
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2007-11-07 17:25:08 | Re: any way for ORDER BY x to imply NULLS FIRST in 8.3? |
| Previous Message | andy | 2007-11-07 17:17:17 | Re: strange timezone problem |