Re: [HACKERS] Odd timezone backend output

2008-05-02 Thread Andrew Sullivan
On Thu, May 01, 2008 at 09:58:09PM -0400, Andrew Chernow wrote: The more I think about it, I personally like the display behavior of NTFS file times over something like EXT3. When I am in EDT, it is useful to have all display times in that zone (regardless of whether that time falls

Re: [HACKERS] Odd timezone backend output

2008-05-02 Thread Andrew Chernow
Andrew Sullivan wrote: On Thu, May 01, 2008 at 09:58:09PM -0400, Andrew Chernow wrote: The more I think about it, I personally like the display behavior of NTFS file times over something like EXT3. When I am in EDT, it is useful to have all display times in that zone (regardless of whether

Re: [HACKERS] Odd timezone backend output

2008-05-02 Thread Andrew Sullivan
On Fri, May 02, 2008 at 09:54:20AM -0400, Andrew Chernow wrote: I prefer offset from UTC, the timezone abbrevs are ambiguos and confusing. So did you read the manual on SET TIME ZONE? TIME ZONE SET TIME ZONE value is an alias for SET timezone TO value. The syntax SET TIME ZONE

Re: [HACKERS] Odd timezone backend output

2008-05-02 Thread Andrew Dunstan
Andrew Chernow wrote: I prefer offset from UTC, the timezone abbrevs are ambiguos and confusing. If I am in a timezone that is currently 4 hours behind UTC, I would prefer all times to display adjusted by that offset. I understand that technically its eastern time and EDT makes no sense

[HACKERS] Odd timezone backend output

2008-05-01 Thread Andrew Chernow
I am confused about the below results. The backend is in EDT but it is converting timestamps into EST ... excluding NOW(). Regardless of the timezone provided, the backend is dishing out EST. [EMAIL PROTECTED] ~]# uname -a 2.6.9-67.0.4.EL #1 Sun Feb 3 06:53:29 EST 2008 i686 athlon i386

Re: [HACKERS] Odd timezone backend output

2008-05-01 Thread Tom Lane
Andrew Chernow [EMAIL PROTECTED] writes: I am confused about the below results. The backend is in EDT but it is converting timestamps into EST ... excluding NOW(). Regardless of the timezone provided, the backend is dishing out EST. Try a date that's actually during the EDT part of the

Re: [HACKERS] Odd timezone backend output

2008-05-01 Thread Andrew Sullivan
On Thu, May 01, 2008 at 09:53:41AM -0400, Andrew Chernow wrote: I am confused about the below results. The backend is in EDT but it is converting timestamps into EST ... excluding NOW(). Regardless of the timezone provided, the backend is dishing out EST. First, this doesn't really belong

Re: [HACKERS] Odd timezone backend output

2008-05-01 Thread Andrew Chernow
Tom Lane wrote: Andrew Chernow [EMAIL PROTECTED] writes: I am confused about the below results. The backend is in EDT but it is converting timestamps into EST ... excluding NOW(). Regardless of the timezone provided, the backend is dishing out EST. Try a date that's actually during the EDT

Re: [HACKERS] Odd timezone backend output

2008-05-01 Thread Andrew Dunstan
Andrew Chernow wrote: Tom Lane wrote: Andrew Chernow [EMAIL PROTECTED] writes: I am confused about the below results. The backend is in EDT but it is converting timestamps into EST ... excluding NOW(). Regardless of the timezone provided, the backend is dishing out EST. Try a date

Re: [HACKERS] Odd timezone backend output

2008-05-01 Thread Andrew Chernow
NTFS adjusts winter file times while in daylight savings The only file times we should ever be interested in are surely epoch times, which should be unaffected by time zones. cheers andrew epoch, or at least non-timezone adjusted times, is the way every modern FS stores file times, no