Thread: CURRENT TIME causes server to shutdown connection
Hello, 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. I've been searching all over for clues about this, and haven't found a thing. If anyone has an idea as to the source of this, that would be great. Thanks, John
"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
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 > >
"John T. Yocum" <john@fluidhosting.com> writes:
> It's version, 7.3.3, I compiled it from source about a week ago.
Hmph. Should work then. Can you get a debugger stack trace from
the backend core dump?
regards, tom lane
Hi all, I couldn't find a command to get the version number of PostgreSQL from a TCP/IP client. How must I do this? Thanks, Marc
Marc, Try Select version(); Steve McAllister > -----Original Message----- > From: pgsql-novice-owner@postgresql.org [mailto:pgsql-novice- > owner@postgresql.org] On Behalf Of M. Bastin > Sent: Monday, 11 August 2003 7:21 PM > To: pgsql-novice@postgresql.org > Subject: [NOVICE] getting PostgreSQL version from TCP/IP client > > Hi all, > > I couldn't find a command to get the version number of PostgreSQL > from a TCP/IP client. How must I do this? > > Thanks, > > Marc > > ---------------------------(end of broadcast)--------------------------- > TIP 8: explain analyze is your friend
Thanks Steve, it works. Are there any other things working with SELECT like this -- or better, where is this documented? Thanks, Marc >Select version(); > > > I couldn't find a command to get the version number of PostgreSQL > > from a TCP/IP client. How must I do this?
The version() function and others is explained in the Postgres Documentation under Functions and Operators/Miscellaneous functions. The use (misuse) of the missing FROM clause is also explained in the documentation under SQL Commands/Select Hope this helps Steve McAllister > -----Original Message----- > From: pgsql-novice-owner@postgresql.org [mailto:pgsql-novice- > owner@postgresql.org] On Behalf Of M. Bastin > Sent: Monday, 11 August 2003 11:22 PM > To: stevemca@optushome.com.au > Cc: pgsql-novice@postgresql.org > Subject: Re: [NOVICE] getting PostgreSQL version from TCP/IP client > > Thanks Steve, it works. Are there any other things working with > SELECT like this -- or better, where is this documented? > > Thanks, > > Marc > > >Select version(); > > > > > I couldn't find a command to get the version number of PostgreSQL > > > from a TCP/IP client. How must I do this? > > ---------------------------(end of broadcast)--------------------------- > TIP 7: don't forget to increase your free space map settings