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@users.sourceforge.net>
To: "RK" <hiding@freemail.hu>
Cc: <pgsql-cygwin@postgresql.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@postgresql.org
>
