Skip site navigation (1) Skip section navigation (2)

Re: UHH - what?? bad date answer suddenly

From: George Weaver <gweaver(at)shaw(dot)ca>
To: RK <hiding(at)freemail(dot)hu>
Cc: pgsql-cygwin(at)postgresql(dot)org
Subject: Re: UHH - what?? bad date answer suddenly
Date: 2004-10-22 15:00:10
Message-ID: 000301c4b847$d5fbe320$6400a8c0@Dell4500 (view raw or flat)
Thread:
Lists: pgsql-cygwin
You have probably experiencing a known problem with cygwin.  See:

http://www.cygwin.com/ml/cygwin/2003-07/msg01016.html


HTH,
George

----- Original Message ----- 
From: "Robert Treat" <xzilla(at)users(dot)sourceforge(dot)net>
To: "RK" <hiding(at)freemail(dot)hu>
Cc: <pgsql-cygwin(at)postgresql(dot)org>
Sent: Friday, October 22, 2004 8:16 AM
Subject: Re: [CYGWIN] UHH - what?? bad date answer suddenly


> On Wednesday 20 October 2004 10:40, RK wrote:
>> Hi all!
>> How could it postgresql on cygwin suddenly started to answer a bad date.
>> Server was running on cygwin for months (!) by now.
>> But from today it started to anser bad date to freguently called
>> now()  funtion.
>> for
>> SELECT NOW() it answered:  2004-08-31.......  ????
>> What has happened?
>> After restarting everything became just fine again
>> cygwin, 7.3 postgresql
>>
>
> PostgreSQL just returns system time for now(), so most likely something
> happened with your system time.  Only other thing I could think of would 
> be
> you were select now() in a transaction that had been open for a few 
> months,
> but that seems unlikely.
>
> -- 
> Robert Treat
> Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org
> 



In response to

Responses

pgsql-cygwin by date

Next:From: Reini UrbanDate: 2004-10-22 16:41:59
Subject: Re: UHH - what?? bad date answer suddenly
Previous:From: Robert TreatDate: 2004-10-22 13:16:18
Subject: Re: UHH - what?? bad date answer suddenly

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group