Re: CURRENT TIME causes server to shutdown connection - Mailing list pgsql-novice

From John T. Yocum
Subject Re: CURRENT TIME causes server to shutdown connection
Date
Msg-id 000f01c35e91$f2473e50$57752f04@YODEMPC1
Whole thread Raw
In response to CURRENT TIME causes server to shutdown connection  ("John T. Yocum" <john@fluidhosting.com>)
Responses Re: CURRENT TIME causes server to shutdown connection
List pgsql-novice
It's version, 7.3.3, I compiled it from source about a week ago.

--John

----- Original Message -----
From: "Tom Lane" <tgl@sss.pgh.pa.us>
To: "John T. Yocum" <john@fluidhosting.com>
Cc: <pgsql-novice@postgresql.org>
Sent: Saturday, August 09, 2003 8:10 AM
Subject: Re: [NOVICE] CURRENT TIME causes server to shutdown connection


> "John T. Yocum" <john@fluidhosting.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
>
>


pgsql-novice by date:

Previous
From: Peter Childs
Date:
Subject: Re: Auto_Increment
Next
From: Jennifer Vargas
Date:
Subject: deletion and many-to-one