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

Re: UHH - what?? bad date answer suddenly

From: Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>
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 13:16:18
Message-ID: 200410220916.18482.xzilla@users.sourceforge.net (view raw or flat)
Thread:
Lists: pgsql-cygwin
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

In response to

Responses

pgsql-cygwin by date

Next:From: George WeaverDate: 2004-10-22 15:00:10
Subject: Re: UHH - what?? bad date answer suddenly
Previous:From: RKDate: 2004-10-21 16:50:12
Subject: cygwin stops....???

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