Re: nasty problem with redhat 6.2 + pg 7.02 - Mailing list pgsql-general

From Thomas Lockhart
Subject Re: nasty problem with redhat 6.2 + pg 7.02
Date
Msg-id 39C84DB2.9C8CA6DD@alumni.caltech.edu
Whole thread Raw
In response to Re: nasty problem with redhat 6.2 + pg 7.02  (leonbloy@sinectis.com.ar)
List pgsql-general
> > The first result (30 sept 23:00:00) is obviously due to
> > a timezone-daylight saving issue.

Fixed in current sources by using mktime() rather than by rotating the
date to 12 noon to try to get the correct time zone (didn't work around
daylight savings time).

> Thomas Lockhart is our lead guy on date/time operations, and it's
> clearly time to get him involved.  Thomas, have you noticed this
> thread?  Any luck reproducing the problem?

Hmm, didn't see the thread (I unsubscribed from -general due to mailing
list overload).

And I don't yet see the problem on my machine:

setenv PGTZ America/Buenos_Aires
lockhart=# set datestyle='postgres,european';

lockhart=# select '01-10-2000'::date::timestamp;
 Sun 01 Oct 00:00:00 2000 ART

lockhart=# select '13-10-2000'::date::timestamp;
 Fri 13 Oct 00:00:00 2000 ART

lockhart=# select '01-10-2000'::date::timestamp;
 Sun 01 Oct 00:00:00 2000 ART

lockhart=# select version();
 PostgreSQL 7.0.2 on i686-pc-linux-gnu, compiled by gcc 2.95.3

This is on a Mandrake 7.1 box with RPMs built from Lamar's source RPMs.
Can someone else reproduce the problem on a RedHat 6.2 box?

                      - Thomas

pgsql-general by date:

Previous
From: dyp
Date:
Subject: Re: Large Objects
Next
From: Andrew.Mason@spektra.co.uk
Date:
Subject: Specifying date locales