From: | "John T(dot) Yocum" <john(at)fluidhosting(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgsql-novice(at)postgresql(dot)org> |
Subject: | Re: CURRENT TIME causes server to shutdown connection |
Date: | 2003-08-09 16:19:01 |
Message-ID: | 000f01c35e91$f2473e50$57752f04@YODEMPC1 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
It's version, 7.3.3, I compiled it from source about a week ago.
--John
----- Original Message -----
From: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "John T. Yocum" <john(at)fluidhosting(dot)com>
Cc: <pgsql-novice(at)postgresql(dot)org>
Sent: Saturday, August 09, 2003 8:10 AM
Subject: Re: [NOVICE] CURRENT TIME causes server to shutdown connection
> "John T. Yocum" <john(at)fluidhosting(dot)com> writes:
> > We've been working to try and solve this issue. On PostgreSQL
> > install(running on RH 7.1), we can't get CURRENT_TIMESTAMP,
> > CURRENT_TIME, or now() to function. All the results is psql reporting
> > the server closed the connection.
>
> Seems like you must have a broken installation of Postgres. What
> version does it claim to be? (If it came with RH 7.1, it's got to be
> pretty ancient anyway ... I'd recommend replacing it with a newer
> release rather than trying to figure out exactly what's gone wrong.)
>
> regards, tom lane
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Jennifer Vargas | 2003-08-09 21:17:15 | deletion and many-to-one |
Previous Message | Peter Childs | 2003-08-09 16:16:47 | Re: Auto_Increment |