From: | Dennis Gearon <gearond(at)cvc(dot)net> |
---|---|
To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
Cc: | Dan Langille <dan(at)langille(dot)org>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: possible time change issue - known problem? |
Date: | 2003-04-07 15:40:16 |
Message-ID: | 3E919BE0.3090707@cvc.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
would this problem have happened using timestamptz?
Martijn van Oosterhout wrote:
> On Mon, Apr 07, 2003 at 08:19:57AM -0400, Dan Langille wrote:
>
>>Looking at the code, I suspect the problem is related to this problem
>>which I can duplicate on my current system: PostgreSQL 7.2.3 on i386-
>>portbld-freebsd4.6, compiled by GCC 2.95.4
>>
>># select current_date, (current_date - interval '1 day')::date;
>> date | date
>>------------+------------
>> 2003-04-07 | 2003-04-05
>>
>>I expect the answer to be 2003-04-06 (i.e. yesterday's date).
>
>
> Out of curiosity, would this weekend be the day you switched to/from
> daylight savings time? Then there were only 23 hours in the day, so 1 day
> ago was actually the 5th.
>
> Anyway, why not just:
>
> select current_date, current_date-1;
> date | ?column?
> ------------+------------
> 2003-04-07 | 2003-04-06
> (1 row)
>
From | Date | Subject | |
---|---|---|---|
Next Message | Ken Godee | 2003-04-07 15:51:41 | Re: chron scripts and pgsql |
Previous Message | Jan Wieck | 2003-04-07 15:38:32 | Re: unable to dump database, toast errors |